-------------- Build: Scripted wizard in Code::Blocks wx2.8.x (compiler: GNU GCC Compiler)---------------
[ 10.0%] Compiling: plugins\scriptedwizard\wiz.cpp
[ 20.0%] Compiling: plugins\scriptedwizard\genericsinglechoicelist.cpp
[ 30.0%] Compiling: plugins\scriptedwizard\buildtargetpanel.cpp
[ 40.0%] Compiling: plugins\scriptedwizard\wizpage.cpp
[ 50.0%] Compiling: plugins\scriptedwizard\infopanel.cpp
[ 60.0%] Compiling: plugins\scriptedwizard\compilerpanel.cpp
[ 70.0%] Compiling: plugins\scriptedwizard\projectpathpanel.cpp
[ 80.0%] Compiling: plugins\scriptedwizard\filepathpanel.cpp
[ 90.0%] Compiling: plugins\scriptedwizard\genericselectpath.cpp
[100.0%] WARNING: Target 'Code::Blocks wx2.8.x - Scripted wizard': Unable to resolve 1 external dependencies:
devel\libcodeblocks.a
Linking dynamic library: devel\share\CodeBlocks\plugins\scriptedwizard.dll
Output size is 2.68 MB
Process terminated with status 0 (2 minutes, 30 seconds)
1- all plugins generate the dll in the right dir, i.e. [trunk]\src\devel\share\CodeBlocks\plugins , but they don't write the manifest ZIP files in [trunk]\src\devel\share\CodeBlocks, so that C::B can't load them at start-up. I've looked and there's no post-build step to make the zip file, as in the contrib-plugins caseThe ZIP files of the "normal plugins" are constructed and copied when you run update.bat. I'm not sure why they are different with the contributed plugins. Any one can explain?
2- there's a warning that devel\libcodeblocks.a cannot be found when building the plugins. I see that this dependency was introduced in r7088. Is this lib needed/generated at all on Win systems? An example is below.I'm also asked about that before, they need to be fixed, but some devs said this is not a big deal. ;)Code-------------- Build: Scripted wizard in Code::Blocks wx2.8.x (compiler: GNU GCC Compiler)---------------
[ 10.0%] Compiling: plugins\scriptedwizard\wiz.cpp
[ 20.0%] Compiling: plugins\scriptedwizard\genericsinglechoicelist.cpp
[ 30.0%] Compiling: plugins\scriptedwizard\buildtargetpanel.cpp
[ 40.0%] Compiling: plugins\scriptedwizard\wizpage.cpp
[ 50.0%] Compiling: plugins\scriptedwizard\infopanel.cpp
[ 60.0%] Compiling: plugins\scriptedwizard\compilerpanel.cpp
[ 70.0%] Compiling: plugins\scriptedwizard\projectpathpanel.cpp
[ 80.0%] Compiling: plugins\scriptedwizard\filepathpanel.cpp
[ 90.0%] Compiling: plugins\scriptedwizard\genericselectpath.cpp
[100.0%] WARNING: Target 'Code::Blocks wx2.8.x - Scripted wizard': Unable to resolve 1 external dependencies:
devel\libcodeblocks.a
Linking dynamic library: devel\share\CodeBlocks\plugins\scriptedwizard.dll
Output size is 2.68 MB
Process terminated with status 0 (2 minutes, 30 seconds)
1- all plugins generate the dll in the right dir, i.e. [trunk]\src\devel\share\CodeBlocks\plugins , but they don't write the manifest ZIP files in [trunk]\src\devel\share\CodeBlocks, so that C::B can't load them at start-up. I've looked and there's no post-build step to make the zip file, as in the contrib-plugins caseThe ZIP files of the "normal plugins" are constructed and copied when you run update.bat. I'm not sure why they are different with the contributed plugins. Any one can explain?
so IMHO it would make sense to generate the zip-files along as a post-build step of each core plugin, as in the case of the contrib plugins, as well as the resources.zip file.I have the same point with you. :)
I'd still be able to run/debug it from devel, without compromising my output dir... :-)
Maybe that's just me, but I'd like to keep everything in the output dir the way it is, but still have the zip files there... I'll do a patch and submit...
So, the question, how to do it?http://stackoverflow.com/questions/708202/git-format-patch-to-be-svn-compatible
Hi All,
...<snip>...
2- there's a warning that devel\libcodeblocks.a cannot be found when building the plugins. I see that this dependency was introduced in r7088. Is this lib needed/generated at all on Win systems? An example is below.
...<snip>...
#!/bin/sh
#
# usage: git-svn-diff [files]
# Generate an SVN-compatible diff against the tip of the tracking branch
TRACKING_BRANCH=`git config --get svn-remote.svn.fetch | sed -e 's/.*:refs\/remotes\///'`
REV=`git svn find-rev $(git rev-list --date-order --max-count=1 $TRACKING_BRANCH)`
git diff --no-prefix $(git rev-list --date-order --max-count=1 $TRACKING_BRANCH) $* |
sed -e "s/^+++ .*/& (working copy)/" -e "s/^--- .*/& (revision $REV)/" \
-e "s/^diff --git [^[:space:]]*/Index:/" \
-e "s/^index.*/===================================================================/"
can I modify the Wiki, or there's some special permission needed?Sure, otherwise it wouldn't be a wiki, right? Just login using your forum's account.
Sure, otherwise it wouldn't be a wiki, right? Just login using your forum's account.ok, I'll do it in the near future....
BTW: This script is Linux only... So at least I cannot try.That's true, I use msysgit, so I have a bash shell to run it. :-)
For the patch: I'll do some testing...Thank you. Btw, this is just the Window's version of it. ;-)
Just login using your forum's account.
Unless it has changed the first letter of your username needs to be upper case to login to the wiki page.Mine is the same, no upper case first letter required.
Unless it has changed the first letter of your username needs to be upper case to login to the wiki page.Mine is the same, no upper case first letter required.
Can we avoid this kind of update? I mean, run zip command only after some XRC files were updated.Uncheck the option "run pre-/ post-build steps even if target is up-to-date".
Aha, it works fine, thanks.Can we avoid this kind of update? I mean, run zip command only after some XRC files were updated.Uncheck the option "run pre-/ post-build steps even if target is up-to-date".