User forums > Help

Compile problems using Beta 6

(1/2) > >>

mike:
Full of excitement, I installed Beta 6 on top of Beta 5. But then the problems came...
The set up: I have a two-project solution, where one produces a library, which the other one (being an EXE) uses. Both projects have MinGW and MSVC targets.

When Linking the "main" MinGW project, I see the followoing messages.

1)
Warning: .drectve `/DEFAULTLIB:"LIBCD" /DEFAULTLIB:"OLDNAMES" ' unrecognized

I guess, the linker options are mixed with those from MSVC.

2)
Linking console executable: main-mingw.exe
library.lib(.msvc-objs/../src/file.o)...: variable '_iob' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details.

Linking with the wrong library (I reserved LIB extension for MSVC and A for MinGW).

Help is needed urgently, before I switched back to Beta 5 :-)

mandrav:
Some of the compiler configuration has changed since beta5. Before we go any further with this, just to make sure that this is not the root of the problem, clear the configuration. To do this, launch codeblocks.exe once with the command line argument "--clear-configuration". This will clear *everything* like it was just installed.

After you do this, does the problem persist?

Yiannis.

mike:
Yes, I still have this problem.

mike:
Moreover, I noticed the the library project does not produce the file "mylib.a" (MinGW target, the file name is specified as the output file), but "libmylib.a" instead:


--- Code: ---
Linking static library: ..\..\Libs\mylib.a
ar.exe: creating ..\..\Libs\libmylib.a
ranlib: '..\..\Libs\mylib.a': No such file

--- End code ---

Anonymous:
I'd like to add that manual inspection of the project file (in a text editor) showed no apparent errors in it - the targets are defined correctly (with regards to compiler options and linked libraries), and the needed C files belong to those targets.

Navigation

[0] Message Index

[#] Next page