CheckLib raises linker errors on Microsoft Visual Studio when library is not found

Bug #591649 reported by Claire on 2010-06-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openWNS SDK
Undecided
Unassigned

Bug Description

Hi,

In the SConstruct file, I am testing the avaibility of a list of libraries with "conf.CheckLib(library)". The linker in Visual Studio raises an error when one library is not found :
"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

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:
> Public bug reported:
>
> Hi,
>
> In the SConstruct file, I am testing the avaibility of a list of libraries with "conf.CheckLib(library)". The linker in Visual Studio raises an error when one library is not found :
> "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
>
>

Hi,

Thanks for your answer! You provide useful information. I solved my problem
meantime.

Greats,
Claire

On Thursday 10 June 2010 17:27:26 you wrote:
> 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:
> > Public bug reported:
> >
> > Hi,
> >
> > In the SConstruct file, I am testing the avaibility of a list of
> > libraries with "conf.CheckLib(library)". The linker in Visual Studio
> > raises an error when one library is not found : "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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers