Pelles C problem
Posted: Thu Jan 03, 2008 2:33 pm
I am having a little problem using RB with Pelles C and the rc format.
The problem is just a few lines at the top of the .rc file.
Maybe an example is easier:
from Pelles:
// RESOURCE SCRIPT generated by "Pelles C for Windows, version 1.00".
#include <windows.h>
#include <commctrl.h>
#include "main.h"
LANGUAGE LANG_ENGLISH,SUBLANG_ENGLISH_US
(the rest is no problem)
now from Resource Builder:
/*********************************************
File: C:\DOCUMENTS AND SETTINGS\P\MY DOCUMENTS\_PROJECTS\C\001_LEARNING_C\FRED\MAIN.RC
Generated by Resource Builder (2.6.4.1).
*********************************************/
/*
OutputExt=res
*/
8001 ICON
MOVEABLE IMPURE LOADONCALL DISCARDABLE
LANGUAGE LANG_ENGLISH, 1
(the rest is no problem)
I can import the .rc file into RB because RB is smart enough to let me "edit as text" then I just comment out the "#include . . ." lines.
The other small differences in the lines starting with "moveable" and "language" don't seem to bother the Pelles compiler.
The trouble is that RB strips those lines on save or export then the IDE can't display the resources because it expects the "#include . . ." lines.
I can't edit the rc file as text in Pelles because it cannot display a rc file as text. I have to start another text editor, add the missing include lines, save the file, close the editor and start the Pelles IDE again.
Can RB be modified to respect the commented lines on import and NOT STRIP those lines on export? If RB would give me the option of "edit as text" on export (then un-comment the #include lines) as well as import it would save me a lot of bother. I think you could do this with an option checkbox in project properties perhaps.
Resource Builder has come a long way since the earlier days when I bought it (and it used to cost twice as much then!) I find it to be a great way to seperate the GUI from the program logic in WIN32 SDK programming. I especially like the ability to open an .exe file and make changes or 'borrow' a resource.
Happy New Year from North Carolina
The problem is just a few lines at the top of the .rc file.
Maybe an example is easier:
from Pelles:
// RESOURCE SCRIPT generated by "Pelles C for Windows, version 1.00".
#include <windows.h>
#include <commctrl.h>
#include "main.h"
LANGUAGE LANG_ENGLISH,SUBLANG_ENGLISH_US
(the rest is no problem)
now from Resource Builder:
/*********************************************
File: C:\DOCUMENTS AND SETTINGS\P\MY DOCUMENTS\_PROJECTS\C\001_LEARNING_C\FRED\MAIN.RC
Generated by Resource Builder (2.6.4.1).
*********************************************/
/*
OutputExt=res
*/
8001 ICON
MOVEABLE IMPURE LOADONCALL DISCARDABLE
LANGUAGE LANG_ENGLISH, 1
(the rest is no problem)
I can import the .rc file into RB because RB is smart enough to let me "edit as text" then I just comment out the "#include . . ." lines.
The other small differences in the lines starting with "moveable" and "language" don't seem to bother the Pelles compiler.
The trouble is that RB strips those lines on save or export then the IDE can't display the resources because it expects the "#include . . ." lines.
I can't edit the rc file as text in Pelles because it cannot display a rc file as text. I have to start another text editor, add the missing include lines, save the file, close the editor and start the Pelles IDE again.
Can RB be modified to respect the commented lines on import and NOT STRIP those lines on export? If RB would give me the option of "edit as text" on export (then un-comment the #include lines) as well as import it would save me a lot of bother. I think you could do this with an option checkbox in project properties perhaps.
Resource Builder has come a long way since the earlier days when I bought it (and it used to cost twice as much then!) I find it to be a great way to seperate the GUI from the program logic in WIN32 SDK programming. I especially like the ability to open an .exe file and make changes or 'borrow' a resource.
Happy New Year from North Carolina