User forums > Using Code::Blocks

Open Watcom problems\questions

(1/3) > >>

madnut.ua:
I try to use Open Watcom with C::B and have some problems with it.

1. I can't specify path of the libs for the linker. wcl386.exe uses wlink directive for it. It's look like:

--- Code: ---wcl386.exe -"LIBPath <path> ..."
--- End code ---
where <path> - it is my path for libs. In C::B I can't specify that directive in Settings->Compiler...->Other->Advanced Options->Others, cause path must be in quotes. If I write some like -"LIBPath", than command will be like: wcl386.exe -"LIBPath"c:\bla\bla... - that is incorrect.
Another way. If I write directly in linker field in commands tab -"LIBPath $libdirs", that will be also incorrect, cause all paths in that directive must delimited by ";", not by space as in C::B.
How can I resolve this problem?

2. I can't link resource file to exe. wcl386.exe writes that it unknown object file. I try to use wrc.exe with -zm option for Microsoft .res compatible file, but it also not work. So, what to do?

3. How can I specify PCH file for the project? I try to use -fh option with specify "watcom.pch" file, but while compiling, this file was recreated for every cpp file in the project.

Who can help me with my problems?

imho, some errors in c::b code:
compilerOW.cpp

--- Code: ---52: m_Programs.MAKE             = wxT("mingw32-make.exe"); // need "wmake.exe"?
...
55: m_Switches.libDirs          = wxT("-L"); // it's not watcom option
...
341: m_RegExes.Add(RegExStruct(_("Note"), cltError, wxT("([A-Za-z0-9_:/\\.-]+)\\(([0-9]+)\\): Note! (.+)"), 3, 1, 2)); // must be cltInfo instead of cltError


--- End code ---

p.s. sorry for "nice" English :)

killerbot:
project (or you can even put on compiler level) : Directories tab (or Linker tab maybe for other settins)

madnut.ua:

--- Quote from: killerbot on January 06, 2007, 11:24:35 pm ---project (or you can even put on compiler level) : Directories tab (or Linker tab maybe for other settins)

--- End quote ---

and what? of course, I write my paths here, but full command line looks like:

--- Code: ---wcl386.exe  -LC:\wxWidgets\lib\wat_dll -LC:\wxWidgets\lib -L..\..\lib -LC:\watcom\lib
--- End code ---
It's incorrect, cause "-L" - is key for gcc, not for watcom.

madnut.ua:
Also I try to create new project with project wizard. wxWidgets application with watcom compiler. But I get error in script. see attach

C::B SVN rev. 3459

[attachment deleted by admin]

stahta01:

--- Quote from: madnut.ua on January 06, 2007, 11:48:07 pm ---
--- Quote from: killerbot on January 06, 2007, 11:24:35 pm ---project (or you can even put on compiler level) : Directories tab (or Linker tab maybe for other settins)

--- End quote ---

and what? of course, I write my paths here, but full command line looks like:

--- Code: ---wcl386.exe  -LC:\wxWidgets\lib\wat_dll -LC:\wxWidgets\lib -L..\..\lib -LC:\watcom\lib
--- End code ---
It's incorrect, cause "-L" - is key for gcc, not for watcom.

--- End quote ---

I am trying to verify that  "-L" works or does NOT work, since I have NOT used Watcom C before it might take awhile for me to reach an answer. The documentation implies that it will NOT work.
Tim S

The testing is starting to confirm that "-L" does NOT work as a way to set patch to look for libraries.

Navigation

[0] Message Index

[#] Next page