Re: [Boost-users] Missing libboost_thread-vc100-mt-s-1_49.lib
Anybody? -- Vimal -----Original Message----- From: Mathew, Vimal Sent: Friday, July 20, 2012 2:32 PM To: boost-users@lists.boost.org Subject: Missing libboost_thread-vc100-mt-s-1_49.lib Hi, I'm trying to build a project using nmake. When I run nmake I get this error message: " LINK : fatal error LNK1104: cannot open file 'libboost_thread-vc100-mt-s-1_49.lib " Could someone tell me what I'm missing please? Thanks, Vimal
On Tue, Jul 24, 2012 at 12:44:05PM +0000, VimalMathew@Eaton.com wrote:
Anybody?
-- Vimal
-----Original Message----- From: Mathew, Vimal Sent: Friday, July 20, 2012 2:32 PM To: boost-users@lists.boost.org Subject: Missing libboost_thread-vc100-mt-s-1_49.lib
Hi, I'm trying to build a project using nmake. When I run nmake I get this error message: " LINK : fatal error LNK1104: cannot open file 'libboost_thread-vc100-mt-s-1_49.lib "
Could someone tell me what I'm missing please?
You're missing the library for Boost.Thread, built like: b2 ^ toolset=msvc-10.0 ^ runtime-link=static ^ link=static ^ variant=release ^ threading=multi ^ --with-thread The naming scheme is explained over at: http://www.boost.org/doc/libs/1_50_0/more/getting_started/windows.html#libra... -- Lars Viklund | zao@acc.umu.se
Built it. Still the same error. Could it be that I'm not calling it correctly in the makefile? This is what I have in my Makefile: CXX=cl/EHsc C=gcc SYMPHONY_PATH=C:/SYMPHONY-5.4.4 BOOST_PATH=C: MEXFLAG= -Wall -O3 -m32 -shared -DMATLAB_MEX_FILE -Wl,--export-all-symbols MATLAB_LIBPATH= -L$(MATLABROOT)/bin/win32 -L$(MATLABROOT)/extern/lib/win32/microsoft MATLAB_INCLPATH= -I$(MATLABROOT)/extern/include MATLAB_LIBS= -lmex -lmx -lmwlapack -lmwblas -leng -ladvapi32 -luser32 -lgdi32 -lkernel32 -lmingwex SYMPHONY_INCLPATH= -I$(SYMPHONY_PATH)/include/coin -I$(SYMPHONY_PATH)/SYMPHONY/include/coin SYMPHONY_LIBPATH= -L$(SYMPHONY_PATH)/SYMPHONY/lib -L$(SYMPHONY_PATH)/lib SYMPHONY_LIBS= -lOsiSym -lSym -lCgl -lOsiClp -lClp -lOsi -lCoinUtils -lm BOOST_INCLPATH= -I$(BOOST_PATH)/boost_1_49_0/boost/numeric/ublas BOOST_LIBPATH= -L$(BOOST_PATH)/boost_1_49_0/stage/lib all: win_multithread win_multithread: $(CXX) -DBOOST_THREAD_USE_LIB -static -O3 -Ic:/boost_1_49_0 $(SYMPHONY_INCLPATH) -L"c:\boost_1_49_0\stage\lib" mex_all_paths_multithread_nograph.cpp -o win32_all_paths_multithread_nograph.exe $(SYMPHONY_LIBPATH) $(SYMPHONY_LIBS) -lboost_thread-mgw45-mt-1_49 -lboost_thread-mgw45-mt-1_49 $(BOOST_INCLPATH) $(BOOST_LIBPATH) @rm -f *.o* -- Vimal -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Lars Viklund Sent: Tuesday, July 24, 2012 8:53 AM To: boost-users@lists.boost.org Subject: Re: [Boost-users] Missing libboost_thread-vc100-mt-s-1_49.lib On Tue, Jul 24, 2012 at 12:44:05PM +0000, VimalMathew@Eaton.com wrote:
Anybody?
-- Vimal
-----Original Message----- From: Mathew, Vimal Sent: Friday, July 20, 2012 2:32 PM To: boost-users@lists.boost.org Subject: Missing libboost_thread-vc100-mt-s-1_49.lib
Hi, I'm trying to build a project using nmake. When I run nmake I get this error message: " LINK : fatal error LNK1104: cannot open file 'libboost_thread-vc100-mt-s-1_49.lib "
Could someone tell me what I'm missing please?
You're missing the library for Boost.Thread, built like: b2 ^ toolset=msvc-10.0 ^ runtime-link=static ^ link=static ^ variant=release ^ threading=multi ^ --with-thread The naming scheme is explained over at: http://www.boost.org/doc/libs/1_50_0/more/getting_started/windows.html#libra... -- Lars Viklund | zao@acc.umu.se _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
On 24.7.2012 16:13, VimalMathew@Eaton.com wrote:
Built it. Still the same error. Could it be that I'm not calling it correctly in the makefile?
Well, you're trying to use CL like you'd be using GCC. Don't do that as they do not share the same command line syntax (e.g. -L is /LIBPATH: and so on). Unless you really want, I'd suggest that you simply make a new VC project instead of playing with Makefiles. That's a lot easier with MSVC. -- Pekka
I tried that.
I get this huge bunch of LNK2019 unresolved external symbol errors. This is one:
mex_all_paths_multithread_nograph.obj : error LNK2019: unresolved external symbol "int __cdecl sym_close_environment(struct SYM_ENVIRONMENT *)" (?sym_close_environment@@YAHPAUSYM_ENVIRONMENT@@@Z) referenced in function "int __cdecl runSYMPHONY_bjm(double *,class boost::numeric::ublas::matrix
Built it. Still the same error. Could it be that I'm not calling it correctly in the makefile?
Well, you're trying to use CL like you'd be using GCC. Don't do that as they do not share the same command line syntax (e.g. -L is /LIBPATH: and so on). Unless you really want, I'd suggest that you simply make a new VC project instead of playing with Makefiles. That's a lot easier with MSVC. -- Pekka _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
On 24.7.2012 16:32, VimalMathew@Eaton.com wrote:
I tried that. I get this huge bunch of LNK2019 unresolved external symbol errors. This is one: mex_all_paths_multithread_nograph.obj : error LNK2019: unresolved external symbol "int __cdecl sym_close_environment(struct SYM_ENVIRONMENT *)" (?sym_close_environment@@YAHPAUSYM_ENVIRONMENT@@@Z) referenced in <ommited>
Do you know why this is happening?
Hi, looks like you're not linking against the Symphony libraries (thus the missing sym_close_environment) (and I guess Matlab libs are next). It's not enough that you specify the library paths, you need to specify the actual libraries too (so convert those -l options and remember to specify the complete name as -l does prefix and append things). You may pass the linker the /VERBOSE option to see what it actually tries to do; Sometimes it's quite useful. (This works mostly "automatically" with Boost as Boost.Config uses certains MSVC specific #pragmas to tell the linker (thru compiler) which libraries to link against so all you need to worry about is the path.) -- Pekka
So I need to explicitly mention Symphony libraries in Configuration Properties->Linker->Input->Additional Dependencies? -- Vimal -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Pekka Seppänen Sent: Tuesday, July 24, 2012 9:56 AM To: boost-users@lists.boost.org Subject: Re: [Boost-users] Missing libboost_thread-vc100-mt-s-1_49.lib On 24.7.2012 16:32, VimalMathew@Eaton.com wrote:
I tried that. I get this huge bunch of LNK2019 unresolved external symbol errors. This is one: mex_all_paths_multithread_nograph.obj : error LNK2019: unresolved external symbol "int __cdecl sym_close_environment(struct SYM_ENVIRONMENT *)" (?sym_close_environment@@YAHPAUSYM_ENVIRONMENT@@@Z) referenced in <ommited>
Do you know why this is happening?
Hi, looks like you're not linking against the Symphony libraries (thus the missing sym_close_environment) (and I guess Matlab libs are next). It's not enough that you specify the library paths, you need to specify the actual libraries too (so convert those -l options and remember to specify the complete name as -l does prefix and append things). You may pass the linker the /VERBOSE option to see what it actually tries to do; Sometimes it's quite useful. (This works mostly "automatically" with Boost as Boost.Config uses certains MSVC specific #pragmas to tell the linker (thru compiler) which libraries to link against so all you need to worry about is the path.) -- Pekka _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
On 24.7.2012 17:07, VimalMathew@Eaton.com wrote:
So I need to explicitly mention Symphony libraries in Configuration Properties->Linker->Input->Additional Dependencies?
Yes. If you dislike that, you may also use #pragma comment(lib, "library.lib") syntax. It's pretty much the same thing. And don't forget to specify the library search paths ;) -- Pekka
-- Vimal
-----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Pekka Seppänen Sent: Tuesday, July 24, 2012 9:56 AM To: boost-users@lists.boost.org Subject: Re: [Boost-users] Missing libboost_thread-vc100-mt-s-1_49.lib
On 24.7.2012 16:32, VimalMathew@Eaton.com wrote:
I tried that. I get this huge bunch of LNK2019 unresolved external symbol errors. This is one: mex_all_paths_multithread_nograph.obj : error LNK2019: unresolved external symbol "int __cdecl sym_close_environment(struct SYM_ENVIRONMENT *)" (?sym_close_environment@@YAHPAUSYM_ENVIRONMENT@@@Z) referenced in <ommited>
Do you know why this is happening?
Hi,
looks like you're not linking against the Symphony libraries (thus the missing sym_close_environment) (and I guess Matlab libs are next). It's not enough that you specify the library paths, you need to specify the actual libraries too (so convert those -l options and remember to specify the complete name as -l does prefix and append things). You may pass the linker the /VERBOSE option to see what it actually tries to do; Sometimes it's quite useful.
(This works mostly "automatically" with Boost as Boost.Config uses certains MSVC specific #pragmas to tell the linker (thru compiler) which libraries to link against so all you need to worry about is the path.)
-- Pekka _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
Thanks Pekka! Specifying the libraries worked! -- Vimal -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Pekka Seppänen Sent: Tuesday, July 24, 2012 10:17 AM To: boost-users@lists.boost.org Subject: Re: [Boost-users] Missing libboost_thread-vc100-mt-s-1_49.lib On 24.7.2012 17:07, VimalMathew@Eaton.com wrote:
So I need to explicitly mention Symphony libraries in Configuration Properties->Linker->Input->Additional Dependencies?
Yes. If you dislike that, you may also use #pragma comment(lib, "library.lib") syntax. It's pretty much the same thing. And don't forget to specify the library search paths ;) -- Pekka
-- Vimal
-----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Pekka Seppänen Sent: Tuesday, July 24, 2012 9:56 AM To: boost-users@lists.boost.org Subject: Re: [Boost-users] Missing libboost_thread-vc100-mt-s-1_49.lib
On 24.7.2012 16:32, VimalMathew@Eaton.com wrote:
I tried that. I get this huge bunch of LNK2019 unresolved external symbol errors. This is one: mex_all_paths_multithread_nograph.obj : error LNK2019: unresolved external symbol "int __cdecl sym_close_environment(struct SYM_ENVIRONMENT *)" (?sym_close_environment@@YAHPAUSYM_ENVIRONMENT@@@Z) referenced in <ommited>
Do you know why this is happening?
Hi,
looks like you're not linking against the Symphony libraries (thus the missing sym_close_environment) (and I guess Matlab libs are next). It's not enough that you specify the library paths, you need to specify the actual libraries too (so convert those -l options and remember to specify the complete name as -l does prefix and append things). You may pass the linker the /VERBOSE option to see what it actually tries to do; Sometimes it's quite useful.
(This works mostly "automatically" with Boost as Boost.Config uses certains MSVC specific #pragmas to tell the linker (thru compiler) which libraries to link against so all you need to worry about is the path.)
-- Pekka _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
No, that file does not exist anywhere on my system.
--
Vimal
-----Original Message-----
From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of John Drescher
Sent: Tuesday, July 24, 2012 8:54 AM
To: boost-users@lists.boost.org
Subject: Re: [Boost-users] Missing libboost_thread-vc100-mt-s-1_49.lib
On Tue, Jul 24, 2012 at 8:44 AM,
Anybody?
Does that file exist in your boost build in the lib folder? I just checked and I have that exact file for x64 under visual studio 2010. John _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
participants (4)
-
John Drescher -
Lars Viklund -
Pekka Seppänen -
VimalMathew＠Eaton.com