CheckLib raises linker errors on Microsoft Visual Studio when library is not found
Bug #591649 reported by
Claire
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openWNS SDK |
New
|
Undecided
|
Unassigned |
Bug Description
Hi,
In the SConstruct file, I am testing the avaibility of a list of libraries with "conf.CheckLib(
"LINK : fatal error LNK1181: cannot open input file 'foo.lib'".
Is there a way to get rid of such an error and to ignore the absence of the library?
By the way, the behaviour is by default like this under Linux... So the difference of behaviour seems to be a bug!
Best Regards
To post a comment you must log in.
Hi,
I'm not really sure if I understand this right?
Are you asking why ./playground install immediately complains if a
library is missing? The reason for that was that often it took long time
to compile just to realize at the end that installation failed because a
library is missing. Therefore the check is done at the start. Also GCC
often printed a lot of "missing symbol" errors and it was hard to find
which missing library is actually causing the problem.
Greats,
Mac
Claire wrote: library) ". The linker in Visual Studio raises an error when one library is not found :
> Public bug reported:
>
> Hi,
>
> In the SConstruct file, I am testing the avaibility of a list of libraries with "conf.CheckLib(
> "LINK : fatal error LNK1181: cannot open input file 'foo.lib'".
> Is there a way to get rid of such an error and to ignore the absence of the library?
>
> By the way, the behaviour is by default like this under Linux... So the
> difference of behaviour seems to be a bug!
>
> Best Regards
>
> ** Affects: openwns-sdk
> Importance: Undecided
> Status: New
>
>