Compiler : Ignore unresolved external links
Compiler : Ignore unresolved external links
Hi,
Should it be possible to have an option to make compiler ignore unresolved external links and simply report them as "warning" ?
It's an important thing when you use .lib file that can use other external .lib file...
Regards,
Fred
Odyssey-Creators
Should it be possible to have an option to make compiler ignore unresolved external links and simply report them as "warning" ?
It's an important thing when you use .lib file that can use other external .lib file...
Regards,
Fred
Odyssey-Creators
Re: Compiler : Ignore unresolved external links
In regular, the linker tries to embedd symbols wich are really needed cause they are called within the binary.freddix wrote:Hi,
Should it be possible to have an option to make compiler ignore unresolved external links and simply report them as "warning" ?
It's an important thing when you use .lib file that can use other external .lib file...
Regards,
Fred
Odyssey-Creators
So in your case of request a nonfunctional appl. would be the result -> so whats your purpose?
Check out OOP support for PB here!
in my case, the compiler try to resolve an external link that is defined but not used.
link to here to understand :
http://www.purebasic.fr/english/viewtop ... highlight=
link to here to understand :
http://www.purebasic.fr/english/viewtop ... highlight=
If they are used, in which .lib ?
I have tried all solutions available over the internet without success.
DevC++, Visual studio, all have options to IGNORE unresolved external links ... it does not prevent compiled programs from running !!!
So, why shouldn't it be possible for PureBASIC ?
Regards,
Fred
I have tried all solutions available over the internet without success.
DevC++, Visual studio, all have options to IGNORE unresolved external links ... it does not prevent compiled programs from running !!!
So, why shouldn't it be possible for PureBASIC ?
Regards,
Fred
Maybe there are diff. revisions of libcp.lib avail. in the www and you do need a specific revision?!
Or they do need the Cdecl calling convention or even aren't exported by using Export "C" { .... }
Or they do need the Cdecl calling convention or even aren't exported by using Export "C" { .... }
Check out OOP support for PB here!