User forums > Using Code::Blocks
[Resolved] Using OpenWatcom compiler in C::B
thomas:
--- Quote from: Eric75000 on September 28, 2007, 12:18:23 pm ---=> Now I'm using C::B Nightly build SVN4491 : what the difference compared to RC2 !!!! :P
--- End quote ---
Basically, everything.
--- Quote ---Where can I config more verbose build logs in C::B please ? (only 5 lines in SVN4491 instead of many many lines in RC2)
--- End quote ---
Compiler settings, rightmost tab, select "full command line".
Eric75000:
Thanks Thomas for your answer !
Build logs are a little more verbose but not enough :? : although none compiler flag is set, when I build my prog, I can see in build log "wcl386.exe -q -c..." and after "wlink.exe option quiet..."
=> This is why I can't see all of the logs : -q flag = operate quietly for compiler, and option quiet = quiet (!) for the linker.
Somebody knows please where can I unset this flag ? I search in Settings/Compiler and debugger and in my project properties but I've found nothing !
Biplab:
--- Quote from: Eric75000 on September 28, 2007, 10:17:44 pm ---Build logs are a little more verbose but not enough :? : although none compiler flag is set, when I build my prog, I can see in build log "wcl386.exe -q -c..." and after "wlink.exe option quiet..."
=> This is why I can't see all of the logs : -q flag = operate quietly for compiler, and option quiet = quiet (!) for the linker.
Somebody knows please where can I unset this flag ? I search in Settings/Compiler and debugger and in my project properties but I've found nothing !
--- End quote ---
Don't worry about that difference. That's hard-coded. It won't affect your project.
Unfortunately the command line options of wlink.exe is not same as of other tools, such as wcl386.exe. So option quiet may seem odd to you but it is the option which wlink.exe uses.
Eric75000:
Hi !
Sorry for my late answer, I was in holidays...
--- Quote ---It won't affect your project.
--- End quote ---
I know, I know !!! :wink:
--- Quote ---That's hard-coded.
--- End quote ---
Argh ! It's too bad that you can't set or unset by yourself this flag ! I know this flag ins't very very important, but I was accustomed at the logs of RC2 version :oops:
So, I have another problem : when I want to compile my prog in OpenWatcom with inline command, I must type in a DOS window :
--- Code: ---wcl386 /l=dos4g my_starfield.c
--- End code ---
I would like to do the same in C::B, so in the build options of my projet, I set the flag "link for the specified OS (define TARGET_OS in custom variables) [-l=[TARGET_OS])" and click "Add" button in the "Custom variables" tabs and type "$(TARGET_OS)" for the key, and "dos4g" for the value...
But, when I build my prog, (F11) I can see in the logs : wcl386.exe -q -c -l=
The compiler take well the flag but not the custom variable $(TARGET_OS) :(
Where I made a mistake ???
(I hope you understand my very very bad english :oops:)
Biplab:
--- Quote from: Eric75000 on October 03, 2007, 04:12:31 pm ---
--- Quote ---That's hard-coded.
--- End quote ---
Argh ! It's too bad that you can't set or unset by yourself this flag ! I know this flag ins't very very important, but I was accustomed at the logs of RC2 version :oops:
--- End quote ---
Ok, I'll change this.
--- Quote from: Eric75000 on October 03, 2007, 04:12:31 pm ---So, I have another problem : when I want to compile my prog in OpenWatcom with inline command, I must type in a DOS window :
--- Code: ---wcl386 /l=dos4g my_starfield.c
--- End code ---
I would like to do the same in C::B, so in the build options of my projet, I set the flag "link for the specified OS (define TARGET_OS in custom variables) [-l=[TARGET_OS])" and click "Add" button in the "Custom variables" tabs and type "$(TARGET_OS)" for the key, and "dos4g" for the value...
But, when I build my prog, (F11) I can see in the logs : wcl386.exe -q -c -l=
The compiler take well the flag but not the custom variable $(TARGET_OS) :(
Where I made a mistake ???
(I hope you understand my very very bad english :oops:)
--- End quote ---
This is a bug. Actually not all linker options are mapped to their equivalent wlink.exe command. It needs to be fixed.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version