News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

rpm packages for C::B?

Started by rickg22, August 03, 2005, 08:00:39 PM

Previous topic - Next topic

rickg22

I was wondering - how hard it is to make RPM packages for Code::Blocks? What are the difficulties and complications?

darklordsatan

Making rpms is a piece of cake. But the difficulties here is that most people havent been able to compile it successfully (Am I right?), so until we have some piece of sourcecode that actually compiles well, with no probs under a Linux box with wx6.1 and else, there should be no prob providing them.

rickg22

Maybe this is going to the extreme, but wouldn't it be easier to add the whole wxWidgets library (i know, it sounds crazy, but it might just work!) so that we compile C::B and our own tested wxWidgets without any problems whatsoever?

Funto

Isn't there a dependency system with RPM packages?
I know the wxWidgets team proposes RPMs for wx2.4 (not for 2.6); it would be possible to precise a dependency towards these RPMs.

darklordsatan >> compiling doesn't seem to be the real big problem now the Makefiles are up-to-date, the problems are the crashes; this is because the developpers mainly work on Windows :(

darklordsatan

Quote from: Funto on August 04, 2005, 12:59:04 AM
compiling doesn't seem to be the real big problem now the Makefiles are up-to-date, the problems are the crashes
I wasnt aware, since my Slack box is broken ATM so I havent had the chance to test it myself.
Well, I guess we need to first make sure it doesnt crash (that much at least :oops:) in order to provide an rpm. Dont know, just MHO.
Probably we need someone to take care of the Linux port? (Im not aware if someone other than yiannis or rick is doing this ATM).

rickg22

Yes, we need a Linux dev in here!

fiammy

The problem is that most Linux distros at the moment have some flavour of wxWidgets 2.5.x standard included. I don't know what happens if you install an older version on the system, but you could get away with it if you just include the static version of the libs.

what is needed for an RPM build is a .spec file. I've never done that before, so I don't know if it is complicated or not.