User forums > Using Code::Blocks

RPM Spec file is ready

<< < (2/5) > >>

afecelis:
Great! fantastic! outstanding!!!!  First time I ever get Codeblocks to run under linux!!!  :D :D Thank you Daniel!!! It also taught me how to build an rpm package. It worked perfectly for Suse 10. I had never been able to compile the source so this is by far a huge success for me!!!

The RPM package I built can be downloaded here:
http://www.danielpatton.com/afecelis/Codeblocks/codeblocks-1.0-cvs.i586.rpm

ps. Mandrav, many thanks for the Irrlicht project template!!  :D

TheTuxKeeper:
I added a new article in the wiki with the current Specfile.
-> Compiling Code::Blocks in RPM based distributions

Happy codeblocking  :D

Daniel

fiammy:
It works, but (yes, there's always a but, not necessarily with 2 't' s :-) ) when I want to build the package on SuSE 10.0 x86_64, the system complains that the paths for the libaries aren't right. On 64-bit systems, the 'lib' directory is replaced with a 'lib64'. I don't know if it is possible to autodetect the 'lib' path on the system?

else, great script. Thanks. It's simple enough to show me how to do a .rpm setup for my own projects, and still it had enough features to make it really usefull.

Thanks.

baboo:
Hello
I installed all the prerequisites for the RPM and this is what i ran:

[root@srv]# rpm -i codeblocks-1.0-cvs.i586.rpm
error: unpacking of archive failed: cpio: Bad magic


Any ideas why? I didnt build the rpm on my machine. It is downloaded from the address from the first post.

Thank you.

I am running Fedora Core 4 on an Athlon 2600+/ 512MB/ 40GB.

TheTuxKeeper:

--- Quote from: baboo on November 03, 2005, 05:08:42 pm ---[root@srv]# rpm -i codeblocks-1.0-cvs.i586.rpm
error: unpacking of archive failed: cpio: Bad magic

Any ideas why? I didnt build the rpm on my machine. It is downloaded from the address from the first post.

Thank you.

I am running Fedora Core 4 on an Athlon 2600+/ 512MB/ 40GB.
--- End quote ---
Don't even try to use binary RPM's compiled for other distribution  :twisted:  Even RPM's of Suse 9.2 doesn't work in Suse 9.3 in many cases. :(

The file are linked to different lib's with different versions and features.

So it's better using the source RPM from the download page and build it yourself. ;)



--- Quote from: fiammy on November 03, 2005, 03:44:08 pm ---It works, but (yes, there's always a but, not necessarily with 2 't' s :-) ) when I want to build the package on SuSE 10.0 x86_64, the system complains that the paths for the libaries aren't right. On 64-bit systems, the 'lib' directory is replaced with a 'lib64'. I don't know if it is possible to autodetect the 'lib' path on the system?
--- End quote ---
Oh, that's a bug in my Specfile !!!

I didn't set the lib path manually. So it's always /usr/lib but your lib path is /usr/lib64.

Add the red marked line to the Specfile:

--- Quote ---%build
  ./bootstrap
  ./configure \
     --prefix=%{_prefix} \
     --libdir=%{_libdir}\
     --exec-prefix=%{_exec_prefix} \
     --datadir=%{_datadir} \
     --sysconfdir=%{_sysconfdir} \
     --with-docdir=%{_docdir} \
     CXXFLAGS="$RPM_OPT_FLAGS" \
     CFLAGS="$RPM_OPT_FLAGS"
  make
--- End quote ---

When you use the source RPM just install it as root:

--- Code: ---rpm -i codeblocks-1.0-rc2.src.rpm
--- End code ---

The Specfile will be in /usr/src/packages/SPECS (codeblocks-rc2.spec).

Thank you

Navigation

[0] Message Index

[#] Next page

[*] Previous page