User forums > Help
Resource compiler directories seems to be ignored
killerbot:
that's not so good, I will try to look at it tomorrow.
Just to make my life a bit easier, could you provide me with a little test project containing an rc file. It has been some time since I have done that (and it was in M$ Visual Studio).
MortenMacFly:
--- Quote from: killerbot on July 18, 2006, 11:28:50 pm ---Just to make my life a bit easier, could you provide me with a little test project containing an rc file. It has been some time since I have done that (and it was in M$ Visual Studio).
--- End quote ---
Right... that's what I'm trying to find hardly, currently. ;-)
iw2nhl:
I created a little project to show the bug and ... it compiled!
So I investigated and found that in previous project I put the directory in 'debug' target, while in the test project, it was in the 'global' target.
Investigating more I found that the 'Policy' combo is set by default to 'Use project options only', while all other 'Policy's are set to 'Append target options to project options'.
So no bug, at least not there but now I ask a little change:
1) can this policy be set as the others by default?
2) when 'Use project options only' is selected, the directory list could be grayed out (not clearing the list, so that it can be reenabled when needed).
Thanks for you help!
iw2nhl:
Attached there is the small project, used to test the bug.
[no attachment because upload is full]
I noticed this thing:
if there is a missing file, the 'Build messages' shows
=== Build finished: 0 errors, 0 warnings ===
You can try this, renaming the resource file 'resource_file.rc' to something else and then rebuild.
Is this right? Isn't there a way to recognize the "missing file" error?
killerbot:
--- Quote ---1) can this policy be set as the others by default?
--- End quote ---
From a first quick look at th code, it should have been the same as the others (append). But when I created a new project it was a very big negative value. Looking at some CB cbp files, some have it at 0, others don't mention the setting (so it should be the default then). Thos that indeed don't mention the setting are on the default value, so that part of the code works. It seems the bug is related to the part of the code that's generating new projects. A first idea I have is unintitialized variable. Will continue to investigate on this, and fix it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version