User forums > Nightly builds
The 17 June 2012 build (8059) is out.
ptDev:
If the required directory structure is to be created from pre- and post-build steps by the plugin projects, maybe adding those steps to the C::B plugin project generated by the wizard would be a good idea.
Jenna:
--- Quote from: ptDev on July 01, 2012, 04:55:05 pm ---If the required directory structure is to be created from pre- and post-build steps by the plugin projects, maybe adding those steps to the C::B plugin project generated by the wizard would be a good idea.
--- End quote ---
the wizard created plugins should create a cbplugin-file (packed library and resources), that can be installed by C::B's pluginmanager.
Doing this in pre- and postbuild steps would make the compiled plugins undeployable.
ptDev:
--- Quote from: jens on July 01, 2012, 05:26:00 pm ---
--- Quote from: ptDev on July 01, 2012, 04:55:05 pm ---If the required directory structure is to be created from pre- and post-build steps by the plugin projects, maybe adding those steps to the C::B plugin project generated by the wizard would be a good idea.
--- End quote ---
the wizard created plugins should create a cbplugin-file (packed library and resources), that can be installed by C::B's pluginmanager.
Doing this in pre- and postbuild steps would make the compiled plugins undeployable.
--- End quote ---
I don't understand what the problem is.
Doing it in the pre- and postbuild steps instead of in deployment would break deployment, of course. But if this step is also done when a build is done, it would make development much easier.
ollydbg:
--- Quote from: MortenMacFly on July 01, 2012, 02:58:24 pm ---So I tend to solution 1: Add the creation of that output folders either to the pre- or post-build steps.
--- End quote ---
I like this solution, because I think each target should contain its own "update" script(not copy or zip other target's data).
I think put the creation of folders in the target's post-build step is better than pre-build :)
This can also solve the problem as Tim said:
--- Quote from: stahta01 on July 01, 2012, 04:24:37 pm ---Calling update.bat will mean that the output folder copy of Code::Blocks can not be used to build the devel copy of code::blocks.
Tim S.
--- End quote ---
Mainly, the update.bat do three things:
1, create necessary folders under devel folder
2, copy/zip necessary XRC files to devel folder
3, copy all the necessary files from devel folder to output folder, and run strip.
I think the step 3 is not necessary when I'm developing/debugging C::B.
ollydbg:
--- Quote from: japplegame on July 01, 2012, 01:32:50 pm ---There is critical bug in C++ parser. If you insert "magic" code in any unit/header file (included in C++ project) then Code::Blocks will hangs up.
Magic code (copy exactly all quote):
--- Quote --- typedef std::enable_if<N > 1, get_type_N<N-1, Tail...>> type;
--- End quote ---
Looks like parser gets stuck on "N > 1". If to surround it by parentheses, then all works fine.
--- End quote ---
The code is toooooo magic for me that I can't understand the grammar, but the parser should not hang in any case, so I will dig into it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version