Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Don't understand why C::B used a monolithic build
takeshimiya:
When compiling C::B:
In C::B autotools build system both monolithic and non-monolithic are supported.
In C::B build system only monolithic is supported.
I'm trying to think if there is any easy way to include support to both... :?
mandrav:
You don't have to use a monolithic wx lib. When I wrote the instructions at the wiki, wx2.6 wasn't even standard in distros so I just used the windows-build-howto as a starting point.
The thing is that in linux wx-config is used, so no matter how you compile it, it will still work correctly.
The only place we "force" you to use a monolithic wx build is the project file. But nothing's stopping you from changing it to use a non-monolithic version.
Finally, I don't understand why people think that *I* make it hard to build C::B in linux :shock:.
I 've put every effort to make the process as easy as in windows, at least. To me, the linux build is *much* easier than the windows one...
takeshimiya:
--- Quote from: mandrav on January 10, 2006, 07:00:27 pm ---To me, the linux build is *much* easier than the windows one...
--- End quote ---
I'm little off-topic but I tried to say the same.
The fact that linux haves something like wx-config (or sdl-config, or gtk-config, ...) makes changing the build options of any library a lot easier.
But in windows there isn't even the concept of a configure, everything is done by hand.
So I'm thinking if we can do a simple "configure"-like system, to achieve something simmilar to what is in linux, in Windows.
Perhaps some AngelScript here and there, embedded (or not) in the Project files.
thomas:
--- Quote from: Takeshi Miya on January 10, 2006, 07:08:48 pm ---So I'm thinking if we can do a simple "configure"-like system, to achieve something simmilar to what is in Windows.
Perhaps some AngelScript here and there, embedded (or not) in the Project files.
--- End quote ---
Why though? It works fine the way it is, there's no benefit in changing it. The more complex and non-standard you make it, the more likely you make an error.
mosfet:
Good news : while I am posting C::B is compiling on my Mandriva 2006.
My error was to follow the wiki.
I have just added wxWidgets rpm for my distrib instead of building a new one as indicated and
after bootstrap, ./configure, make.
So indeed C::B compiles fine with any version.
My mistake
--- Quote from: mandrav on January 10, 2006, 07:00:27 pm ---You don't have to use a monolithic wx lib. When I wrote the instructions at the wiki, wx2.6 wasn't even standard in distros so I just used the windows-build-howto as a starting point.
The thing is that in linux wx-config is used, so no matter how you compile it, it will still work correctly.
The only place we "force" you to use a monolithic wx build is the project file. But nothing's stopping you from changing it to use a non-monolithic version.
Finally, I don't understand why people think that *I* make it hard to build C::B in linux :shock:.
I 've put every effort to make the process as easy as in windows, at least. To me, the linux build is *much* easier than the windows one...
--- End quote ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version