Full file path in dll

Question

1.00/5 (1 vote)

See more:

Hi,

I have a c++ program that compiles to a dll.

When i open the dll in a text editor i noticed that in some part of the dll i can actually see a full path to the source files i.e c:\myproject\myfile.h

I have noticed that this happens when i use macro in my code with __FILE__ and when using 3rdparty projects such as boost or opencv

Is there any way that i can prevent the full file path to be written to the dll?

Thanks,
Ron

Posted 27-Apr-15 3:06am

babbbam

Updated 27-Apr-15 3:29am

Chris Maunder772.7K

v2

Add a Solution

Comments

Sergey Alexandrovich Kryukov 27-Apr-15 9:19am

Normally, should be no trace of source files at all. How can I know how can you put them in?
—SA

2 solutions

Solution 2

you must build the dll in release mode. Check the compiler settings in your project.

In a release build these macro should not get compiled in the binary output.

Maybe you should look WHERE the release dll is build. :-O

Posted 27-Apr-15 3:28am

KarstenK

Comments

Kornfeld Eliyahu Peter 27-Apr-15 9:32am

That's not enough - if you use these macros in code that are part of the release code it still will be there...

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Kornfeld Eliyahu Peter · Accepted Answer · 2015-04-27T03:23:00

Solution 1

When you are using predefined macros like __FILE__ the compiler (at the pre-processing stage) puts the evaluated value of the macro in the binary created. For __FILE__ that value is the full path to the file as loaded by the pre-processor...

If you do not want to see it don't use it or use it only in debug mode and hide (with #define and #ifdef) when compiling for release...

Posted 27-Apr-15 3:23am

Kornfeld Eliyahu Peter

Updated 27-Apr-15 3:30am

Chris Maunder772.7K

v3

Comments

babbbam 27-Apr-15 9:36am

Thanks for the answer @KornfeldEliyahuPeter, however as i mentioned, i am using 3rdparty such as boost and opencv and they are outputing the full path to the dll...

Kornfeld Eliyahu Peter 27-Apr-15 10:05am

It is possible that you are using a statically linked version of the 3rd party and __FILE__ used there so it becomes part of your code...