Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
wxExecute problems on first start...
Folco:
Ah ok, thanks.
ollydbg:
--- Quote from: MortenMacFly on May 17, 2012, 04:23:43 pm ---
--- Quote from: Folco on May 17, 2012, 04:03:22 pm ---(Morten, your link seems to be dead)
--- End quote ---
For the record, this is our "task list":
--- Quote from: MortenMacFly ---Task:
- Fix an issue, that when having a workspace with many targets, macro manager in combination with CC does not work initially with global vars
* have a ws with many project - all relying on a global var, e.g. "wx"
* open the workspace
* quickly hit compile workspace to compile all which would need resolved #wx global vars
* -> error at the first wx include
* in the debug log, wait for the final
"Updating class browser...
Class browser updated."
* try again - it works now
This is a serious bug but I don't understand why the macro manager depends on CC or vice versa. Not easy to catch!
Question: does macro manager issue an error if a global var cannot be resolved or access is denied to settings or alike?!
--- End quote ---
--- End quote ---
I just tried several times, but I can't reproduce this issue.
I just open the "ContribPlugins.workspace", and hit "build workspace" quickly, and I have no such issue.
MortenMacFly:
--- Quote from: ollydbg on May 18, 2012, 02:02:07 am ---I just tried several times, but I can't reproduce this issue.
--- End quote ---
"Nice"... ???
--- Quote from: ollydbg on May 18, 2012, 02:02:07 am ---I just open the "ContribPlugins.workspace", and hit "build workspace" quickly, and I have no such issue.
--- End quote ---
I have an own workspace that consist of C::B's core, all contrib plugins and additional plugins (so a WS of ~80 targets). Maybe that's why. Try a really, really large WS with as many projects as you have...
oBFusCATed:
For me the bug happens with single project :(
Jenna:
I was just bitten by it the first time (after switching my OS to fedora).
I can just start building a second time and it works.
I'm not sure, but it only seems to happen, if CC is still parsing. I will try if I can reproduce it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version