User forums > Help

Problems making CB for OSX from wiki instructions

<< < (4/11) > >>

bnilsson:
So, where does this take us?
Assuming that the load process is the way it is for a good reason, what's missing is the generation of the proper files with the proper names in the proper places?

Pecan:

--- Quote from: bnilsson on September 25, 2006, 02:53:49 pm ---So, where does this take us?
Assuming that the load process is the way it is for a good reason, what's missing is the generation of the proper files with the proper names in the proper places?


--- End quote ---

The manifest files are delivered in SVN. And with the usual SVN build, the manifest is ziped into pluginname.zip by update.bat or ./update .

What the MAC build needs to do is: zip the manifest.xml that accompanies all plugins into a pluginname.zip and place it into .../share/codeblocks .

On my OSX10.3, the names in .../share/codeblocks/plugins end up being pluginname.so . So I changed ./update to simply zip the manifest from .../trunk/src/plugins/pluginname/manifest.xml to .../trunk/src/devel/share/codeblocks .

Dont forget the contribs if you use any. I ziped the ones I use by hand.



--- Code: ---echo Compressing plugins lib resources //(pecan 2006/9/23)
${ZIPCMD} -j9 ${RESDIR}/libastyle.zip plugins/astyle/resources/manifest.xml  > /dev/null
${ZIPCMD} -j9 ${RESDIR}/libautosave.zip plugins/autosave/manifest.xml  > /dev/null
${ZIPCMD} -j9 ${RESDIR}/libclasswizard.zip plugins/classwizard/resources/manifest.xml  > /dev/null
${ZIPCMD} -j9 ${RESDIR}/libcodecompletion.zip plugins/codecompletion/resources/manifest.xml  > /dev/null
${ZIPCMD} -j9 ${RESDIR}/libcompiler.zip plugins/compilergcc/resources/manifest.xml  > /dev/null
${ZIPCMD} -j9 ${RESDIR}/libdefaultmimehandler.zip plugins/defaultmimehandler/resources/manifest.xml  > /dev/null
${ZIPCMD} -j9 ${RESDIR}/libdebugger.zip plugins/debuggergdb/resources/manifest.xml  > /dev/null
${ZIPCMD} -j9 ${RESDIR}/libscriptedwizard.zip plugins/scriptedwizard/resources/manifest.xml > /dev/null
${ZIPCMD} -j9 ${RESDIR}/libtodo.zip plugins/todo/resources/manifest.xml  > /dev/null

--- End code ---

afb:
I still don't see why the zip names can't be the same on Linux and Macintosh,
i.e. why we shouldn't strip the "lib" prefix from the so before looking for a zip...

Pecan:

--- Quote from: afb on September 25, 2006, 04:07:43 pm ---I still don't see why the zip names can't be the same on Linux and Macintosh,
i.e. why we shouldn't strip the "lib" prefix from the so before looking for a zip...

--- End quote ---

I think you can. Then you don't have to mess with the ./update.
But you'd have to do a rename of plugins or some such.

Wait. Doesn't MAC memorize the .so libname in the lib somehow? I seem to remember getting into trouble doing a lib rename. But maybe that was just on a .dylib.

If the rename works on MAC, the the search for the manifest will work the same for Linux and MAC.

For me (I use a home grown Codeblocks-unixMac.cbp), I can simply change the project file to output the libname without the lib. Then it'll all works as delivered.

afb:
Ehrm, I did not suggest replacing the bundle name (libplugin.so)
all I suggested was to make it look for a "plugin.zip" instead...

Did you look at the patch ? I just changed "GTK" to "GTK || Mac"
and it works just like before, when using the regular autoconf.

Navigation

[0] Message Index

[#] Next page

[*] Previous page