Developer forums (C::B DEVELOPMENT STRICTLY!) > Compiler Framework Redesign

XML based compilers resources

(1/2) > >>

daniloz:
Hi All,

I've noticed that the XML files from src\plugins\compilergcc\resources\compilers are not copied into devel\..., which caused my compiled version not to work.

Here's a patch to solve it, by using a post-build step to copy/update them.


--- Code: ---Index: src/CodeBlocks.cbp
===================================================================
--- src/CodeBlocks.cbp    (revision 8771)
+++ src/CodeBlocks.cbp    (working copy)
@@ -372,6 +373,8 @@
  <Add after="cmd /c if not exist devel\share\CodeBlocks mkdir devel\share\CodeBlocks" />
  <Add after="zip -jq9 devel\share\CodeBlocks\compiler.zip plugins\compilergcc\resources\manifest.xml plugins\compilergcc\resources\*.xrc" />
  <Add after='cmd /c &quot;cd plugins\compilergcc\resources &amp; zip -0 -q ..\..\..\devel\share\CodeBlocks\compiler.zip images\*.png images\16x16\*.png&quot;' />
+ <Add after="cmd /c if not exist devel\share\CodeBlocks\compilers mkdir devel\share\CodeBlocks\compilers" />
+ <Add after="cmd /c xcopy plugins\compilergcc\resources\compilers\*.* devel\share\CodeBlocks\compilers /y" />
  <Mode after="always" />
  </ExtraCommands>
  </Target>

--- End code ---

MortenMacFly:

--- Quote from: daniloz on January 07, 2013, 11:02:54 am ---Here's a patch to solve it, by using a post-build step to copy/update them.

--- End quote ---
Are you aware that this is done by the update.bat script which you need to run after compilation anyways?

daniloz:

--- Quote from: MortenMacFly on January 07, 2013, 11:38:21 am ---
--- Quote from: daniloz on January 07, 2013, 11:02:54 am ---Here's a patch to solve it, by using a post-build step to copy/update them.

--- End quote ---
Are you aware that this is done by the update.bat script which you need to run after compilation anyways?

--- End quote ---
Yes, I'm aware, but I don't want to run it after compilation because I want to be able to run directly from devel without overwriting my output version.

I don't know if I'm doing something which is considered wrong or evil by the devs, but I use my output dir as my production dir and devel as my dev playground version.  ;)

MortenMacFly:

--- Quote from: daniloz on January 07, 2013, 11:54:28 am ---I don't know if I'm doing something which is considered wrong or evil by the devs, but I use my output dir as my production dir and devel as my dev playground version.  ;)

--- End quote ---
Its not evil, but then you would need to do the same thing for all contrib plugins, where it is needed, too. Thats why I was asking... Or do you not use / compile contrib plugins?

daniloz:

--- Quote from: MortenMacFly on January 07, 2013, 12:09:58 pm ---
--- Quote from: daniloz on January 07, 2013, 11:54:28 am ---I don't know if I'm doing something which is considered wrong or evil by the devs, but I use my output dir as my production dir and devel as my dev playground version.  ;)

--- End quote ---
Its not evil, but then you would need to do the same thing for all contrib plugins, where it is needed, too. Thats why I was asking... Or do you not use / compile contrib plugins?

--- End quote ---
I do use (and compile) the contrib plugins, but I haven't had problems so far because all the others rely on ZIP files which are generated by the post-build steps anyway.

BTW, I'm not very acquainted with the inner details of the plugin system, but why does these XML files for the compiler plugin have to be directly copied, while all other plugins put their files inside a ZIP file?

Navigation

[0] Message Index

[#] Next page

Go to full version