User forums > Using Code::Blocks

[Resolved] Using OpenWatcom compiler in C::B

<< < (3/5) > >>

Biplab:
I've fixed the bug (Not expanding the Custom variables). It's in revision 4505.

Regarding changing the option quiet you can do this. Go to Settings > Compiler & debugger > Other settings. Now click on the Advanced button. There you can change the linker command by editing that line and removing option quiet from that.

If you find any other bugs, please feel free to report it.

Eric75000:
Hello everybody !

Biplab : many many thanks to take your precious time to help a little frenchy like me by changing C::B code to allow modifying logs flags in Openwatcom compiler & linker : it's so cool :P
=> I'm now in 4515 revision and, for this, it works like I want !!!! :mrgreen: :mrgreen: :mrgreen:

But for the "custom variables", I must do a mistake (but I don't know where) because it doesn't work :( instead of you've fixed the bug !
It's like exactly the same that previously :
--- Quote ---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=
--- End quote ---

 :cry: :cry: :cry:

Biplab:

--- Quote from: Eric75000 on October 09, 2007, 07:06:56 pm ---But for the "custom variables", I must do a mistake (but I don't know where) because it doesn't work :( instead of you've fixed the bug !
It's like exactly the same that previously :
--- Quote ---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=
--- End quote ---

 :cry: :cry: :cry:

--- End quote ---

I guess you're making some mistakes. This is what happens in my PC. I've used -l=$(TARGET_OS) compiler options and a custom variable TARGET_OS with value nt_win for the project. :)


--- Quote ----------------- Build: Debug in Test ---------------
[ 50.0%] wcl386.exe -q -c -l=nt_win -xs -wx  -d2    -iC:\watcom\h -iC:\watcom\h\nt  -fo=obj\Debug\main.obj main.cpp
[100.0%] wlink.exe option quiet system nt_win debug watcom all  LIBP  C:\watcom\lib386;C:\watcom\lib386\nt file obj\Debug\main.obj name bin\Debug\Test.exe 
Output size is 67.58 KB
Process terminated with status 0 (0 minutes, 0 seconds)
0 errors, 0 warnings
--- End quote ---

You may upload your project file as a zip file so that we may have a look at it.

Eric75000:

--- Quote ---You may upload your project file as a zip file so that we may have a look at it.
--- End quote ---
Really, you could do that for me ? :D

=> Here are all my [little] projet... (it's to learn how using 13h video mode like old PC 80's demo)

Thanks in advance for your precious help !!!


[attachment deleted by admin]

Eric75000:
:cry: No answer :cry:

=> Nobody is interrested more by my prog ???

Biplab ? Sorry but, can U help me please ? :oops:

Navigation

[0] Message Index

[#] Next page

[*] Previous page