Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
exchndl related patch because win32/lib folder is empty in SVN
stahta01:
Still building several contrib projects; wxContribItem and wxSmith are the main ones to change output below:
--- Code: ---$ tree src/lib
src/lib
|-- contrib
| |-- SpellChecker
| | |-- libhunspell.a
| | `-- libwxSpellChecker.a
| |-- devpak_plugin
| | `-- libbz2.a
| |-- help_plugin
| | |-- libbzip2.a
| | `-- libz.a
| |-- source_exporter
| | `-- libwxPdfDocument.a
| `-- wxSmithPlot
| `-- libMathPlot.a
|-- libcodeblocks.a
|-- libdepslib.a
|-- libsqplus.a
|-- libsqstdlib.a
|-- libsquirrel.a
|-- libtxml.a
|-- libwxchartctrl.a
|-- libwxflatnotebook.a
|-- libwxpropgrid.a
`-- libwxscintilla_cb.a
6 directories, 17 files
--- End code ---
Tim S.
stahta01:
MortenMacFly: Link to updated patches. Tried PM, also.
https://github.com/stahta01/cb_misc/tree/master/Patches/Git-am
oBFusCATed:
--- Quote from: MortenMacFly on September 08, 2015, 08:25:15 am ---I don't know if complete flattening is good. Third party libs may be needed in different versions (as the bzip lib, for example). So if the folders are "too flat" you would probably overwrite a library with a wrong version which is bad. Every target (being plugin or SDK) should have an own folder to cope with such.
--- End quote ---
Keep in mind that this will lead to a disaster if it happens on linux!
There we are building with every symbol being visible. Which means that the first symbol named X to load wins and will be called, no matter if the code is expecting the other symbol. This is named symbol collision and it is pretty bad.
Why are there two different bzip implementations? As far as I can see they are named differently (bz2 and bzip2). Are they the same thing? Same API?
stahta01:
--- Quote from: oBFusCATed on September 08, 2015, 11:16:45 pm ---
--- Quote from: MortenMacFly on September 08, 2015, 08:25:15 am ---I don't know if complete flattening is good. Third party libs may be needed in different versions (as the bzip lib, for example). So if the folders are "too flat" you would probably overwrite a library with a wrong version which is bad. Every target (being plugin or SDK) should have an own folder to cope with such.
--- End quote ---
Keep in mind that this will lead to a disaster if it happens on linux!
There we are building with every symbol being visible. Which means that the first symbol named X to load wins and will be called, no matter if the code is expecting the other symbol. This is named symbol collision and it is pretty bad.
Why are there two different bzip implementations? As far as I can see they are named differently (bz2 and bzip2). Are they the same thing? Same API?
--- End quote ---
I have no idea why there is two different bzip implementations; will check in the furture about why.
Here's the layout I am trying to use in Linux; still have a ways to go before the patch is ready.
Any reasons why this layout is bad? Or ways to improve it?
--- Code: ---$ tree src/lib src/lib28 src/lib30
src/lib
+-- contrib
| +-- help_plugin
| +-- libbzip2.a
| +-- libz.a
+-- libdepslib.a
+-- libsqplus.a
+-- libsqstdlib.a
+-- libsquirrel.a
+-- libtxml.a
src/lib28
+-- contrib
| +-- source_exporter
| | +-- libwxPdfDocument.a
| +-- SpellChecker
| +-- libwxSpellChecker.a
+-- libwxscintilla_cb.a
src/lib30
+-- contrib
| +-- source_exporter
| | +-- libwxPdfDocument.a
| +-- SpellChecker
| +-- libwxSpellChecker.a
+-- libwxscintilla_cb.a
8 directories, 13 files
--- End code ---
Tim S.
oBFusCATed:
One thing for sure - don't build or use libz.a. We should use the system provided version on linux!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version