News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

Problems linking with Visual Studio 2005 Professional

Started by Hideaki, March 24, 2009, 03:21:44 AM

Previous topic - Next topic

Hideaki

I'm having problems linking a simple program(and anything for that matter) with Code::Blocks using the Visual Studio 2005 Professional compiler.

This is the error I get:
-------------- Build: Debug in test ---------------

main.cpp
Linking console executable: bin\Debug\test.exe
link: extra operand `/LIBPATH:C:\\Program Files\\Microsoft Visual Studio 8\\VC\\lib'
Try `link --help' for more information.
Process terminated with status 1 (0 minutes, 0 seconds)
0 errors, 0 warnings


The same compile will work fine with Visual Studio 2008 Pro, but I'd like to use 2005 for a project I've already been working on.

Hideaki

#1
Well, it turns out it has nothing to do with code::blocks but with the fact that I have cygwin in my path. Is there a reason why Code::Blocks is launching link.exe from the path instead of directly from the specified location?

I fixed this by specifying the full path to link.exe(C:\Program Files\Microsoft Visual Studio 8\VC\bin\link.exe) in Code::Block's compiler settings.

Jenna

Which version of C::B do you use.

This issue (not respecting the path-order implied by settting the path in toolchain tab sometimes) should be fixed in svn r5344.

Hideaki

Quote from: jens on March 24, 2009, 07:27:55 AM
Which version of C::B do you use.

This issue (not respecting the path-order implied by settting the path in toolchain tab sometimes) should be fixed in svn r5344.


I'm using 8.02.

Jenna

Quote from: Hideaki on March 24, 2009, 07:34:04 AM
Quote from: jens on March 24, 2009, 07:27:55 AM
Which version of C::B do you use.

This issue (not respecting the path-order implied by settting the path in toolchain tab sometimes) should be fixed in svn r5344.


I'm using 8.02.

In this case you should either update to a recent nightly build or wait for the next release to have this issue fixed.