Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » Releasing U++ » Working on new release system...
Re: Working on new release system... [message #22328 is a reply to message #20365] Fri, 03 July 2009 19:02 Go to previous messageGo to next message
andrei_natanael is currently offline  andrei_natanael
Messages: 262
Registered: January 2009
Experienced Member
This week i've tried to make a chroot of Ubuntu Jaunty 32bit and build an U++ app from it. The size of chroot is 647.2 MB, but with care it can be reduced. What chroot say about the application:
Quote:

can@can-laptop :~/chroot/jaunty/home/can/upp-svn/out/GCC.Debug.Debug_full.G ui.Shared$ ls
AddressBookXML2
can@can-laptop :~/chroot/jaunty/home/can/upp-svn/out/GCC.Debug.Debug_full.G ui.Shared$ file AddressBookXML2
AddressBookXML2: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not stripped
can@can-laptop :~/chroot/jaunty/home/can/upp-svn/out/GCC.Debug.Debug_full.G ui.Shared$
can@can-laptop :~/chroot/jaunty/home/can/upp-svn/out/GCC.Debug.Debug_full.G ui.Shared$ ldd AddressBookXML2
linux-gate.so.1 => (0xf7f4f000)
libgtk-x11-2.0.so.0 => /usr/lib32/libgtk-x11-2.0.so.0 (0xf7b83000)
libgdk-x11-2.0.so.0 => /usr/lib32/libgdk-x11-2.0.so.0 (0xf7af6000)
libatk-1.0.so.0 => /usr/lib32/libatk-1.0.so.0 (0xf7ada000)
libgdk_pixbuf-2.0.so.0 => /usr/lib32/libgdk_pixbuf-2.0.so.0 (0xf7ac0000)
libpangocairo-1.0.so.0 => /usr/lib32/libpangocairo-1.0.so.0 (0xf7ab4000)
libfontconfig.so.1 => /usr/lib32/libfontconfig.so.1 (0xf7a87000)
libXext.so.6 => /usr/lib32/libXext.so.6 (0xf7a77000)
libXrender.so.1 => /usr/lib32/libXrender.so.1 (0xf7a6c000)
libXinerama.so.1 => /usr/lib32/libXinerama.so.1 (0xf7a69000)
libXi.so.6 => /usr/lib32/libXi.so.6 (0xf7a5f000)
libXrandr.so.2 => /usr/lib32/libXrandr.so.2 (0xf7a57000)
libXcursor.so.1 => /usr/lib32/libXcursor.so.1 (0xf7a4e000)
libXfixes.so.3 => /usr/lib32/libXfixes.so.3 (0xf7a48000)
libpango-1.0.so.0 => /usr/lib32/libpango-1.0.so.0 (0xf7a05000)
libcairo.so.2 => /usr/lib32/libcairo.so.2 (0xf798b000)
libX11.so.6 => /usr/lib32/libX11.so.6 (0xf789c000)
libgobject-2.0.so.0 => /usr/lib32/libgobject-2.0.so.0 (0xf785e000)
libgmodule-2.0.so.0 => /usr/lib32/libgmodule-2.0.so.0 (0xf7859000)
libglib-2.0.so.0 => /usr/lib32/libglib-2.0.so.0 (0xf77a0000)
libdl.so.2 => /lib32/libdl.so.2 (0xf779c000)
libXft.so.2 => /usr/lib32/libXft.so.2 (0xf7788000)
libpthread.so.0 => /lib32/libpthread.so.0 (0xf776f000)
libz.so.1 => /usr/lib32/libz.so.1 (0xf7759000)
libpng12.so.0 => /usr/lib32/libpng12.so.0 (0xf7733000)
libstdc++.so.6 => /usr/lib32/libstdc++.so.6 (0xf7643000)
libm.so.6 => /lib32/libm.so.6 (0xf761d000)
libgcc_s.so.1 => /usr/lib32/libgcc_s.so.1 (0xf760e000)
libc.so.6 => /lib32/libc.so.6 (0xf74ab000)
libXcomposite.so.1 => /usr/lib32/libXcomposite.so.1 (0xf74a7000)
libXdamage.so.1 => /usr/lib32/libXdamage.so.1 (0xf74a4000)
libgio-2.0.so.0 => /usr/lib32/libgio-2.0.so.0 (0xf7435000)
libpangoft2-1.0.so.0 => /usr/lib32/libpangoft2-1.0.so.0 (0xf740c000)
libfreetype.so.6 => /usr/lib32/libfreetype.so.6 (0xf7395000)
libexpat.so.1 => /usr/lib32/libexpat.so.1 (0xf736e000)
libXau.so.6 => /usr/lib32/libXau.so.6 (0xf7369000)
libpixman-1.so.0 => /usr/lib32/libpixman-1.so.0 (0xf7326000)
libdirectfb-1.0.so.0 => /usr/lib32/libdirectfb-1.0.so.0 (0xf72c0000)
libfusion-1.0.so.0 => /usr/lib32/libfusion-1.0.so.0 (0xf72b7000)
libdirect-1.0.so.0 => /usr/lib32/libdirect-1.0.so.0 (0xf72a2000)
libxcb-render-util.so.0 => /usr/lib32/libxcb-render-util.so.0 (0xf729c000)
libxcb-render.so.0 => /usr/lib32/libxcb-render.so.0 (0xf7294000)
libxcb.so.1 => /usr/lib32/libxcb.so.1 (0xf727a000)
libpcre.so.3 => /lib32/libpcre.so.3 (0xf7248000)
/lib/ld-linux.so.2 (0xf7f50000)
libselinux.so.1 => /lib32/libselinux.so.1 (0xf722d000)
libXdmcp.so.6 => /usr/lib32/libXdmcp.so.6 (0xf7228000)

So far so god... It runs on my system because I have installed 32bit libs but i want to test if it runs on a 32bit environment. If there are any volunteers to test it, we may make a step forward and setup also 32bit build. Here is the test application.
(Feedback expected Wink )
Re: Working on new release system... [message #22330 is a reply to message #20365] Fri, 03 July 2009 23:57 Go to previous messageGo to next message
amrein is currently offline  amrein
Messages: 278
Registered: August 2008
Location: France
Experienced Member
I understand people wanting to play with chrooted distro because it's a cool Linux behaviour. I did it too a few mouths ago. But at the end, for me, Virtual Machine is really the way to go.

Faster to do, easier to manage, smaller to produce, easy to add new build target and you keep total control. Windows, Linux, BSD, whatever, 32 bit, 64 bit, Intel/AMD, ARM and PPC. What could be better?
Re: Working on new release system... [message #22331 is a reply to message #22330] Sat, 04 July 2009 00:38 Go to previous messageGo to next message
andrei_natanael is currently offline  andrei_natanael
Messages: 262
Registered: January 2009
Experienced Member
amrein wrote on Sat, 04 July 2009 00:57

I understand people wanting to play with chrooted distro because it's a cool Linux behaviour. I did it too a few mouths ago. But at the end, for me, Virtual Machine is really the way to go.

Faster to do, easier to manage, smaller to produce, easy to add new build target and you keep total control. Windows, Linux, BSD, whatever, 32 bit, 64 bit, Intel/AMD, ARM and PPC. What could be better?

Well, i know it's simple to use a VM but it use more memory than a chroot system and with less memory the compilation take more, Anyway i think Mirek want to build 32bit directly in 64bit environment without chroot.
Re: Working on new release system... [message #22356 is a reply to message #22331] Tue, 07 July 2009 19:58 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13986
Registered: November 2005
Ultimate Member
andrei_natanael wrote on Fri, 03 July 2009 18:38

amrein wrote on Sat, 04 July 2009 00:57

I understand people wanting to play with chrooted distro because it's a cool Linux behaviour. I did it too a few mouths ago. But at the end, for me, Virtual Machine is really the way to go.

Faster to do, easier to manage, smaller to produce, easy to add new build target and you keep total control. Windows, Linux, BSD, whatever, 32 bit, 64 bit, Intel/AMD, ARM and PPC. What could be better?

Well, i know it's simple to use a VM but it use more memory than a chroot system and with less memory the compilation take more, Anyway i think Mirek want to build 32bit directly in 64bit environment without chroot.


Well, right now I have to say I am quite happy with 'src' to cover POSIX systems.

VMs are fine, I am only afraid about managing all these VMs.

Another consideration is that googlecode space is limited (to 2GB of uploads). Maybe we really need distro flavors only to be uploaded to sf.net.

Mirek
Re: Working on new release system... [message #22357 is a reply to message #22253] Tue, 07 July 2009 20:01 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13986
Registered: November 2005
Ultimate Member
amrein wrote on Sat, 27 June 2009 17:51

For rpm automatic release, we need a script to generate standard Makefile without theide.

Ultimate++ still doesn't have a great command line configure/build system like cmake, automake/autoconf, ant or qmake/tmake. I understood that you didn't want extra dependencies.



I guess we are sort of past this point. Universal POSIX 'src' release is created each night. And it seems to work across platforms just fine.

Mirek

P.S.: Welcome back Smile
Re: Working on new release system... [message #22475 is a reply to message #20365] Sat, 18 July 2009 01:06 Go to previous messageGo to next message
amrein is currently offline  amrein
Messages: 278
Registered: August 2008
Location: France
Experienced Member
Hi luzr Smile

I'm working on 'upp.spec' to be able to build rpm.


What I've found:

- I can't use the default Makefile in root directory because it's for locale build only. Does things like copying theide into ~/ . So I use uppsrc/Makefile instead.

- I can't use the default uppsrc/Makefile without modifying a few variables (LIBPATH, CINC, ...) because of different 64 bit library paths and different include directory paths between Linux distributions. I fixed in the spec file using distribution default paths (I use pkg-config). No problemo.

- I can't automatically add svn version into the rpm spec file (svn can't do that as cvs could) and I don't know when a new release will be out. So to build the rpm you need to submit the package version number and current date like this:

# rpmbuild -tb --define 'version 1314' --define "date $(LC_TIME=En date '+%a %b %d %Y')" upp-x11-src-1314.tar.gz

(Note: this is an example. This won't work at present because upp-x11-src-1314.tar.gz doesn't include the new spec file)


I have just two issues remaining before committing:

1. No default icon for U++ ide. Can't find theide-48.png anymore in svn nor in upp-x11-src-1314.tar.gz.

2. Bad png name in theide.desktop since 2008.1. Should be theide and not theide.png. Here is the patch:


$ cat SOURCES/upp-src-2008.1.fix_png_name_in_desktop_file
diff -p -up ./uppsrc/ide/theide.desktop.fix_png_name_in_desktop_file ./uppsrc/ide/theide.desktop
--- ./uppsrc/ide/theide.desktop.fix_png_name_in_desktop_file 2008-07-28 23:02:06.000000000 +0200
+++ ./uppsrc/ide/theide.desktop 2008-08-17 19:26:10.000000000 +0200
@@ -5,7 +5,7 @@ GenericName=TheIDE
Comment=IDE for cross-platform C++ development
MimeType=application/x-upp
Exec=theide
-Icon=theide.png
+Icon=theide
Terminal=false
Type=Application
Categories=Application;Development;C++


Regards
Re: Working on new release system... [message #22477 is a reply to message #22475] Sat, 18 July 2009 02:55 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13986
Registered: November 2005
Ultimate Member
amrein wrote on Fri, 17 July 2009 19:06

Hi luzr Smile

I'm working on 'upp.spec' to be able to build rpm.


What I've found:

- I can't use the default Makefile in root directory because it's for locale build only. Does things like copying theide into ~/ . So I use uppsrc/Makefile instead.



Well, the default Makefile is for manual building only. That part does not change very often, I think using uppsrc/Makefile is the correct there.

Quote:


- I can't use the default uppsrc/Makefile without modifying a few variables (LIBPATH, CINC, ...) because of different 64 bit library paths and different include directory paths between Linux distributions.



I guess the simple solution, already in use, is to put all different path variants in there. Neither compiler or linker complains about missing directories.

So if you have a suggestion about missing path variants, just post them here Smile

Quote:


- I can't automatically add svn version into the rpm spec file (svn can't do that as cvs could) and I don't know when a new release will be out. So to build the rpm you need to submit the package version number and current date like this:



Check svnversion.

Mirek
Re: Working on new release system... [message #22487 is a reply to message #20365] Sat, 18 July 2009 19:40 Go to previous messageGo to next message
amrein is currently offline  amrein
Messages: 278
Registered: August 2008
Location: France
Experienced Member
New version already commited but I still have the two issue.


To answer your question, here is how I build theide in the rpm spec file:

# make -C uppsrc \
-e LIBPATH=$(pkg-config --libs-only-L x11 freetype2 gtk+-2.0 glib-2.0 cairo pango atk) \
-e CINC=" -I. $(pkg-config --cflags x11 freetype2 gtk+-2.0 glib-2.0 cairo pango atk)" \
-e UPPOUT="$PWD/out/" \
-e OutFile="$PWD/out/ide.out"



Here is how I build GCC.bm:

# INCLUDEDIR=$( pkg-config --cflags x11 freetype2 gtk+-2.0 glib-2.0 cairo pango atk | awk ' { gsub ( / /, "" ) ; gsub ( /-I/, ";" ) ; sub ( /;/, "" ) ; print $0 }' )
LIBDIR=$( pkg-config --libs-only-L x11 freetype2 gtk+-2.0 glib-2.0 cairo pango atk | awk ' { gsub ( / /, "" ) ; gsub ( /-I/, ";" ) ; sub ( /;/, "" ) ; print $0 }' )

cat > %{buildroot}/%{_datadir}/%{name}/GCC.bm << EOF
BUILDER = "GCC";
COMPILER = "g++";
DEBUG_INFO = "2";
DEBUG_BLITZ = "1";
DEBUG_LINKMODE = "1";
DEBUG_OPTIONS = "-O0";
DEBUG_FLAGS = "";
RELEASE_BLITZ = "0";
RELEASE_LINKMODE = "1";
RELEASE_OPTIONS = "-O1 -ffunction-sections";
RELEASE_SIZE_OPTIONS = "-Os -finline-limit=20";
RELEASE_FLAGS = "";
DEBUGGER = "gdb";
PATH = "";
INCLUDE = "$INCLUDEDIR";
LIB = "$LIBDIR";
REMOTE_HOST = "";
REMOTE_OS = "";
REMOTE_TRANSFER = "";
REMOTE_MAP = "";
LINKMODE_LOCK = "0";
EOF


I still have those two issues remaining:

1. No default icon for U++ ide. Can't find theide-48.png anymore in svn nor in upp-x11-src-1314.tar.gz.

2. Bad png name in theide.desktop since 2008.1. Should be theide and not theide.png in theide.desktop file.
Re: Working on new release system... [message #22491 is a reply to message #22487] Sun, 19 July 2009 03:37 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13986
Registered: November 2005
Ultimate Member
amrein wrote on Sat, 18 July 2009 13:40


I still have those two issues remaining:

1. No default icon for U++ ide. Can't find theide-48.png anymore in svn nor in upp-x11-src-1314.tar.gz.



IMO we can take it from previous versions. Where should I put it?

Quote:


2. Bad png name in theide.desktop since 2008.1. Should be theide and not theide.png in theide.desktop file.


Not even sure what theide.desktop is :)\

Mirek
Re: Working on new release system... [message #22525 is a reply to message #22491] Wed, 22 July 2009 15:45 Go to previous messageGo to next message
amrein is currently offline  amrein
Messages: 278
Registered: August 2008
Location: France
Experienced Member
luzr wrote on Sun, 19 July 2009 03:37


IMO we can take it from previous versions. Where should I put it?


Previously it was in "uppsrc/ide/theide-48.png" Cool


luzr wrote on Sun, 19 July 2009 03:37

Quote:

2. Bad png name in theide.desktop since 2008.1. Should be theide and not theide.png in theide.desktop file.

Not even sure what theide.desktop is Smile


This file is an application launcher used by Linux desktop environment like Gnome, KDE, XFE, ... ( www.freedesktop.org/wiki/Specifications/desktop-entry-spec ).

It's here: "uppsrc/ide/theide.desktop".

Re: Working on new release system... [message #22602 is a reply to message #20365] Thu, 30 July 2009 09:48 Go to previous messageGo to next message
amrein is currently offline  amrein
Messages: 278
Registered: August 2008
Location: France
Experienced Member
1. I've attached theide-48.png to this message.

2. The desktop file patch, generated with "diff":


$ cat SOURCES/upp-src-2008.1.fix_png_name_in_desktop_file

diff -p -up ./uppsrc/ide/theide.desktop.fix_png_name_in_desktop_file ./uppsrc/ide/theide.desktop
--- ./uppsrc/ide/theide.desktop.fix_png_name_in_desktop_file    2008-07-28 23:02:06.000000000 +0200
+++ ./uppsrc/ide/theide.desktop 2008-08-17 19:26:10.000000000 +0200
@@ -5,7 +5,7 @@ GenericName=TheIDE
 Comment=IDE for cross-platform C++ development
 MimeType=application/x-upp
 Exec=theide
-Icon=theide.png
+Icon=theide
 Terminal=false
 Type=Application
 Categories=Application;Development;C++
Re: Working on new release system... [message #22623 is a reply to message #22602] Sat, 01 August 2009 12:36 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13986
Registered: November 2005
Ultimate Member
amrein wrote on Thu, 30 July 2009 03:48

1. I've attached theide-48.png to this message.

2. The desktop file patch, generated with "diff":


$ cat SOURCES/upp-src-2008.1.fix_png_name_in_desktop_file

diff -p -up ./uppsrc/ide/theide.desktop.fix_png_name_in_desktop_file ./uppsrc/ide/theide.desktop
--- ./uppsrc/ide/theide.desktop.fix_png_name_in_desktop_file    2008-07-28 23:02:06.000000000 +0200
+++ ./uppsrc/ide/theide.desktop 2008-08-17 19:26:10.000000000 +0200
@@ -5,7 +5,7 @@ GenericName=TheIDE
 Comment=IDE for cross-platform C++ development
 MimeType=application/x-upp
 Exec=theide
-Icon=theide.png
+Icon=theide
 Terminal=false
 Type=Application
 Categories=Application;Development;C++



Thank you, applied.

One thing is not clear to me yet:

Was you able to compile upp-*-src.tar.gz without changes? (just using make / make install)?

Mirek
Re: Working on new release system... [message #22630 is a reply to message #20365] Sat, 01 August 2009 20:04 Go to previous messageGo to next message
amrein is currently offline  amrein
Messages: 278
Registered: August 2008
Location: France
Experienced Member
Quote:

One thing is not clear to me yet:

Was you able to compile upp-*-src.tar.gz without changes? (just using make / make install)?

Mirek


Compiled without changes, yes.

- I used make + custom parameters to compile (see previous post).
- I didn't use 'make install' because the script doesn't copy U++ files where it should. I do this part directly in the rpm '.spec' file.
- I create my own GCC.bm file (as show in previous post, using rpmbuild macro).


This works with upp-x11-src-1438.tar.gz and with previous releases.

But upp-x11-src-1438.tar.gz and other don't have the spec file included so this file is external.

If you want to create automatic rpm build, it will be a pleasure to help out.
Re: Working on new release system... [message #22766 is a reply to message #20365] Wed, 12 August 2009 10:31 Go to previous messageGo to next message
amrein is currently offline  amrein
Messages: 278
Registered: August 2008
Location: France
Experienced Member
Will there be an automatic rpm build system for each new release or do you want me to upload my rpms on sourceforge?
Re: Working on new release system... [message #22767 is a reply to message #22766] Wed, 12 August 2009 10:36 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13986
Registered: November 2005
Ultimate Member
amrein wrote on Wed, 12 August 2009 04:31

Will there be an automatic rpm build system for each new release or do you want me to upload my rpms on sourceforge?


Right now, we have stepped back in this:

Nightly builds are -src and -win32 only. Announced releases should come each 14 days (+/-), koldo will copy nightly build to sf.net and based on it, release maintainers will create platform specific packages and individualy upload to sf.net.

So, the sort answer is: YES. But wait for sources to appear on sf.net (as signal that we called some particular svn revision a "release").

Mirek

[Updated on: Wed, 12 August 2009 10:37]

Report message to a moderator

Re: Working on new release system... [message #23215 is a reply to message #22767] Tue, 29 September 2009 13:55 Go to previous messageGo to next message
amrein is currently offline  amrein
Messages: 278
Registered: August 2008
Location: France
Experienced Member
Could you include trunk/linux_scripts/rpm/upp.spec in next official release? I need it to be able to build rpm packages.
Re: Working on new release system... [message #23283 is a reply to message #23215] Wed, 07 October 2009 11:14 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13986
Registered: November 2005
Ultimate Member
amrein wrote on Tue, 29 September 2009 07:55

Could you include trunk/linux_scripts/rpm/upp.spec in next official release? I need it to be able to build rpm packages.


Official release? Why? How?

Mirek
Re: Working on new release system... [message #23328 is a reply to message #20365] Sat, 10 October 2009 15:26 Go to previous messageGo to next message
amrein is currently offline  amrein
Messages: 278
Registered: August 2008
Location: France
Experienced Member
Quote:

Official release?


upp-x11-src-1517.tar.gz, upp-x11-src-1607.tar.gz, ...

Quote:

How?


upp.spec can be anywhere in the tar.gz directories. The rpmbuild tool will find it anywhere.

Quote:

Why?


Any rpm based distribution will know how to build binary packages (x86, x64, src.rpm, ...) from the tar.gz and It will be easier for me to build packages with my already configured virtual machines.
Re: Working on new release system... [message #23331 is a reply to message #23328] Sun, 11 October 2009 10:02 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13986
Registered: November 2005
Ultimate Member
amrein wrote on Sat, 10 October 2009 09:26

Quote:

Official release?


upp-x11-src-1517.tar.gz, upp-x11-src-1607.tar.gz, ...

Quote:

How?


upp.spec can be anywhere in the tar.gz directories. The rpmbuild tool will find it anywhere.

Quote:

Why?


Any rpm based distribution will know how to build binary packages (x86, x64, src.rpm, ...) from the tar.gz and It will be easier for me to build packages with my already configured virtual machines.


I see, OK, that is reasonable (and interesting).

Hopefully done, check the next nightly build.

In the process, I have moved upp.spec file to uppbox/Scripts (so that it can be edited in Scripts package).

Mirek

Re: Working on new release system... [message #23421 is a reply to message #20365] Sun, 18 October 2009 17:00 Go to previous messageGo to previous message
amrein is currently offline  amrein
Messages: 278
Registered: August 2008
Location: France
Experienced Member
I don't have write access to the repository so here is a patch:


Index: trunk/uppsrc/ide/theide.desktop
===================================================================
--- trunk/uppsrc/ide/theide.desktop     (révision 1634)
+++ trunk/uppsrc/ide/theide.desktop     (copie de travail)
@@ -8,5 +8,5 @@
 Icon=theide
 Terminal=false
 Type=Application
-Categories=Application;Development;C++
+Categories=Application;Development;IDE;C++;
 StartupNotify=false
Index: trunk/uppbox/Scripts/upp.spec
===================================================================
--- trunk/uppbox/Scripts/upp.spec       (révision 1634)
+++ trunk/uppbox/Scripts/upp.spec       (copie de travail)
@@ -90,12 +90,14 @@
 install -d %{buildroot}/%{_bindir}
 install -d %{buildroot}/%{_desktopdir}
 install -d %{buildroot}/%{_datadir}/icons/hicolor/48x48/apps
+install -d %{buildroot}/%{_datadir}/pixmaps
 install -d %{buildroot}/%{_datadir}/%{name}

 install out/ide.out %{buildroot}/%{_bindir}/theide

 cp -p uppsrc/ide/theide.desktop %{buildroot}/%{_desktopdir}/theide.desktop
 cp -p uppsrc/ide/theide-48.png %{buildroot}/%{_datadir}/icons/hicolor/48x48/apps/theide.png
+cp -p uppsrc/ide/theide-48.png %{buildroot}/%{_datadir}/pixmaps/theide.png

 cp -a bazaar %{buildroot}/%{_datadir}/%{name}/
 # cp -a Common %{buildroot}/%{_datadir}/%{name}/
@@ -147,6 +149,7 @@
 %{_bindir}/theide
 %{_desktopdir}/theide.desktop
 %{_datadir}/icons/hicolor/48x48/apps/theide.png
+%{_datadir}/pixmaps/theide.png
 %dir %{_datadir}/%{name}
 %{_datadir}/%{name}/*

Previous Topic: Regular releases reactivated
Next Topic: Releasing deb package issue
Goto Forum:
  


Current Time: Sat Jun 22 22:15:57 CEST 2024

Total time taken to generate the page: 0.02138 seconds