Re: [CMake] CPack and RPM packages
2011/3/8 Laszlo Papp :
> I could not still build cmake.. But I did this modification
> locally you suggested and that is the output:
>
> CPack: Create package using RPM
> CPack: Install projects
> CPack: - Run preinstall target for: Gluon
> CPack: - Install project: Gluon
> CPack: Create package
> CPackRPM: Will use GENERATED spec file:
> /home/meego/gluon/build/_CPack_Packages/Linux/RPM/SPECS/gluon.spec
> CPack: - package: /home/meego/gluon/build/Gluon-0.71.0.rpm.rpm generated.
the double .rpm.rpm extension seems awkward but may be this is a
copy/paste typo?
You can check the content of the generated rpm file using:
$ rpm -qpl /home/meego/gluon/build/Gluon-0.71.0.rpm
and get the meta-info with:
$ rpm -qpi /home/meego/gluon/build/Gluon-0.71.0.rpm
> It was a quite slow process after the spec file generation, but it
> seems to work. I do really hope someone can fix the arm - qemu - cmake
> thread hanging issues otherwise no idea how to get this functionality
> working "officially"...
I'm glad it's working now.
Ok now that you can build an rpm,
I think you should really look at the way you install files.
in
https://projects.kde.org/projects/playground/games/gluon/repository/revisions/master/entry/core/CMakeLists.txt
you define:
set(INCLUDE_INSTALL_DIR ${CMAKE_INSTALL_PREFIX}/include
CACHE PATH "The subdirectory relative to the install prefix where
header files will be installed.")
set(LIB_INSTALL_DIR ${CMAKE_INSTALL_PREFIX}/lib${LIB_SUFFIX}
CACHE PATH "The subdirectory relative to the install prefix where
libraries will be installed.")
set(SHARE_INSTALL_DIR ${CMAKE_INSTALL_PREFIX}/share
CACHE PATH "The subdiractory relative to the install prefix where
data and other files will be installed.")
and then
install(TARGETS GluonCore RUNTIME DESTINATION bin LIBRARY DESTINATION
${LIB_INSTALL_DIR} ARCHIVE DESTINATION ${LIB_INSTALL_DIR} FRAMEWORK
DESTINATION ${LIB_INSTALL_DIR})
so you use absolute destination install path.
If you do so, CPackRPM will automatically set those files as "%config"
files, i.e. files that shouldn't be replaced blindly during an update
or suppressed
when the rpm is removed. (%config are files typically installed in /etc/)
You may end-up with an rpm which does not behave "as usual".
What you [should|could] do to avoid this behavior is:
set(INCLUDE_INSTALL_DIR include CACHE PATH "The
subdirectory relative to the install prefix where header files will be
installed.")
set(LIB_INSTALL_DIR lib${LIB_SUFFIX}CACHE PATH "The
subdirectory relative to the install prefix where libraries will be
installed.")
set(SHARE_INSTALL_DIR share CACHE PATH "The
subdiractory relative to the install prefix where data and other files
will be installed.")
that what _INSTALL_DIR will become relative and CPackRPM should
behave more the way you expect it should.
In order to be consistent with your DEB packaging you may tell
CPackRPM the dependencies you know:
set(CPACK_RPM_PACKAGE_REQUIRES "libqt4-gui >= 4.6, libqt4-opengl >=
4.6, libopenal1, libsndfile1, libvorbis0a, libgles2")
in the hand-crafted sepc file there is a post-install script.
This can be added with CPackRPM too:
set(CPACK_RPM_POST_INSTALL_SCRIPT_FILE your-post-script.sh)
the file your-post-script.sh should be available (may be in the build
tree or source tree) when the RPM
is built by CPackRPM.
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
My familiar did a package as an interim solution and let us see whether or not this version can be integrated into the 1.2 MeeGo release or just later. http://forum.meego.com/showthread.php?p=18810#post18810 Best Regards, Laszlo Papp On Tue, Mar 8, 2011 at 7:59 AM, Laszlo Papp wrote: > I could not still build cmake.. But I did this modification > locally you suggested and that is the output: > > CPack: Create package using RPM > CPack: Install projects > CPack: - Run preinstall target for: Gluon > CPack: - Install project: Gluon > CPack: Create package > CPackRPM: Will use GENERATED spec file: > /home/meego/gluon/build/_CPack_Packages/Linux/RPM/SPECS/gluon.spec > CPack: - package: /home/meego/gluon/build/Gluon-0.71.0.rpm.rpm generated. > > It was a quite slow process after the spec file generation, but it > seems to work. I do really hope someone can fix the arm - qemu - cmake > thread hanging issues otherwise no idea how to get this functionality > working "officially"... > > Best Regards, > Laszlo PApp > > On Tue, Mar 8, 2011 at 12:53 AM, Eric Noulard wrote: >> 2011/3/8 Laszlo Papp : >>> On Tue, Mar 8, 2011 at 12:45 AM, Eric Noulard >>> wrote: 2011/3/8 Laszlo Papp : > Well: http://public.kitware.com/Bug/view.php?id=11595 > That is fixed in cmake 2.8.4. > Changelog: http://www.cmake.org/pipermail/cmake/2011-February/042839.html > "CPackRPM fix bug 0011595 : Can't generate RPMs (on FC11...)" > > I am trying to build this version now on MeeGo since the available > binary one is 2.8.3. But if it is fixed in 2.8.4, I wonder why you did > not know it ? I do know this bug, I fixed it. I'm just a mere human being and I did not recognize your symptom as being the same as the refered bug. I am really sorry for the wasted time, yours and mine :-/. >>> >>> No idea whether or not that will be the solution, but >>> >>> It is hilarious, I cannot run the cmake ../ properly on the version >>> 2.8.4... I mean it always enters an "endless loop" at random point, >>> but all the time. I heard qemu+cmake is scary, but still >> >>>I did never use such combination, I let other comment on that one. >>> How can I build the newest version of the cmake ? Cmake freezes all >>> the time from the shadow build directory It is more than quite >>> /pesky/. >> >> Concerning CPackRPM main issue, would try to >> >> 1) backup the CMake 2.8.3 , CPackRPM.cmake file >> 2) Edit CPackRPM.cmake file and change: >> >> %install >> if [ -e $RPM_BUILD_ROOT ]; >> then >> mv \"\@CPACK_TOPLEVEL_DIRECTORY\@/tmpBBroot/*\" $RPM_BUILD_ROOT >> else >> mv \"\@CPACK_TOPLEVEL_DIRECTORY\@/tmpBBroot\" $RPM_BUILD_ROOT >> fi >> >> to >> %install >> if [ -e $RPM_BUILD_ROOT ]; >> then >> rm -rf $RPM_BUILD_ROOT >> fi >> mv \"\@CPACK_TOPLEVEL_DIRECTORY\@/tmpBBroot\" $RPM_BUILD_ROOT >> >> then rerun cpack. >> >> >> -- >> Erk >> Membre de l'April - « promouvoir et défendre le logiciel libre » - >> http://www.april.org >> > ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
I could not still build cmake.. But I did this modification locally you suggested and that is the output: CPack: Create package using RPM CPack: Install projects CPack: - Run preinstall target for: Gluon CPack: - Install project: Gluon CPack: Create package CPackRPM: Will use GENERATED spec file: /home/meego/gluon/build/_CPack_Packages/Linux/RPM/SPECS/gluon.spec CPack: - package: /home/meego/gluon/build/Gluon-0.71.0.rpm.rpm generated. It was a quite slow process after the spec file generation, but it seems to work. I do really hope someone can fix the arm - qemu - cmake thread hanging issues otherwise no idea how to get this functionality working "officially"... Best Regards, Laszlo PApp On Tue, Mar 8, 2011 at 12:53 AM, Eric Noulard wrote: > 2011/3/8 Laszlo Papp : >> On Tue, Mar 8, 2011 at 12:45 AM, Eric Noulard wrote: >>> 2011/3/8 Laszlo Papp : Well: http://public.kitware.com/Bug/view.php?id=11595 That is fixed in cmake 2.8.4. Changelog: http://www.cmake.org/pipermail/cmake/2011-February/042839.html "CPackRPM fix bug 0011595 : Can't generate RPMs (on FC11...)" I am trying to build this version now on MeeGo since the available binary one is 2.8.3. But if it is fixed in 2.8.4, I wonder why you did not know it ? >>> >>> I do know this bug, I fixed it. >>> >>> I'm just a mere human being and I did not recognize your symptom >>> as being the same as the refered bug. >>> >>> I am really sorry for the wasted time, yours and mine :-/. >> >> No idea whether or not that will be the solution, but >> >> It is hilarious, I cannot run the cmake ../ properly on the version >> 2.8.4... I mean it always enters an "endless loop" at random point, >> but all the time. I heard qemu+cmake is scary, but still > >>I did never use such combination, I let other comment on that one. >> How can I build the newest version of the cmake ? Cmake freezes all >> the time from the shadow build directory It is more than quite >> /pesky/. > > Concerning CPackRPM main issue, would try to > > 1) backup the CMake 2.8.3 , CPackRPM.cmake file > 2) Edit CPackRPM.cmake file and change: > > %install > if [ -e $RPM_BUILD_ROOT ]; > then > mv \"\@CPACK_TOPLEVEL_DIRECTORY\@/tmpBBroot/*\" $RPM_BUILD_ROOT > else > mv \"\@CPACK_TOPLEVEL_DIRECTORY\@/tmpBBroot\" $RPM_BUILD_ROOT > fi > > to > %install > if [ -e $RPM_BUILD_ROOT ]; > then > rm -rf $RPM_BUILD_ROOT > fi > mv \"\@CPACK_TOPLEVEL_DIRECTORY\@/tmpBBroot\" $RPM_BUILD_ROOT > > then rerun cpack. > > > -- > Erk > Membre de l'April - « promouvoir et défendre le logiciel libre » - > http://www.april.org > ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
2011/3/8 Laszlo Papp : > On Tue, Mar 8, 2011 at 12:45 AM, Eric Noulard wrote: >> 2011/3/8 Laszlo Papp : >>> Well: http://public.kitware.com/Bug/view.php?id=11595 >>> That is fixed in cmake 2.8.4. >>> Changelog: http://www.cmake.org/pipermail/cmake/2011-February/042839.html >>> "CPackRPM fix bug 0011595 : Can't generate RPMs (on FC11...)" >>> >>> I am trying to build this version now on MeeGo since the available >>> binary one is 2.8.3. But if it is fixed in 2.8.4, I wonder why you did >>> not know it ? >> >> I do know this bug, I fixed it. >> >> I'm just a mere human being and I did not recognize your symptom >> as being the same as the refered bug. >> >> I am really sorry for the wasted time, yours and mine :-/. > > No idea whether or not that will be the solution, but > > It is hilarious, I cannot run the cmake ../ properly on the version > 2.8.4... I mean it always enters an "endless loop" at random point, > but all the time. I heard qemu+cmake is scary, but still >I did never use such combination, I let other comment on that one. > How can I build the newest version of the cmake ? Cmake freezes all > the time from the shadow build directory It is more than quite > /pesky/. Concerning CPackRPM main issue, would try to 1) backup the CMake 2.8.3 , CPackRPM.cmake file 2) Edit CPackRPM.cmake file and change: %install if [ -e $RPM_BUILD_ROOT ]; then mv \"\@CPACK_TOPLEVEL_DIRECTORY\@/tmpBBroot/*\" $RPM_BUILD_ROOT else mv \"\@CPACK_TOPLEVEL_DIRECTORY\@/tmpBBroot\" $RPM_BUILD_ROOT fi to %install if [ -e $RPM_BUILD_ROOT ]; then rm -rf $RPM_BUILD_ROOT fi mv \"\@CPACK_TOPLEVEL_DIRECTORY\@/tmpBBroot\" $RPM_BUILD_ROOT then rerun cpack. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
1st run: ca -- The C compiler identification is GNU -- The CXX compiler identification is GNU -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Looking for C++ include iostream -- Looking for C++ include iostream - found -- Check for STD namespace -- Check for STD namespace - found -- Check for ANSI scope -- Check for ANSI scope - found -- Check for sstream -- Check for sstream - found -- Looking for unsetenv -- Looking for unsetenv - found -- Looking for environ -- Looking for environ - not found. -- Checking whether header cstdio is available -- Checking whether header cstdio is available - yes -- Checking for Large File Support -- Checking for Large File Support - yes -- Checking whether STL classes are in std namespace -- Checking whether STL classes are in std namespace - yes -- Checking whether ANSI stream headers are available -- Checking whether ANSI stream headers are available - yes -- Checking whether ANSI streams are in std namespace -- Checking whether ANSI streams are in std namespace - yes -- Checking whether ANSI string stream is available -- Checking whether ANSI string stream is available - yes -- Checking whether header cstddef is available -- Checking whether header cstddef is available - yes -- Checking whether stl string has operator!= for char* -- Checking whether stl string has operator!= for char* - yes -- Checking whether stl has iterator_traits Deadlock-like feeling on the user side except that I can kill the process - 2nd run: -- The C compiler identification is GNU -- The CXX compiler identification is GNU -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Looking for C++ include iostream -- Looking for C++ include iostream - found -- Check for STD namespace -- Check for STD namespace - found -- Check for ANSI scope -- Check for ANSI scope - found -- Check for sstream "Endless loop" feeling again here. - 3rd run: cmake -DCMAKE_INSTALL_PREFIX=/usr .. -- The C compiler identification is GNU -- The CXX compiler identification is GNU -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Looking for C++ include iostream -- Looking for C++ include iostream - found -- Check for STD namespace -- Check for STD namespace - found -- Check for ANSI scope -- Check for ANSI scope - found -- Check for sstream -- Check for sstream - found -- Looking for unsetenv -- Looking for unsetenv - found -- Looking for environ -- Looking for environ - not found. -- Checking whether header cstdio is available -- Checking whether header cstdio is available - yes -- Checking for Large File Support -- Checking for Large File Support - yes -- Checking whether STL classes are in std namespace -- Checking whether STL classes are in std namespace - yes -- Checking whether ANSI stream headers are available -- Checking whether ANSI stream headers are available - yes -- Checking whether ANSI streams are in std namespace -- Checking whether ANSI streams are in std namespace - yes -- Checking whether ANSI string stream is available -- Checking whether ANSI string stream is available - yes -- Checking whether header cstddef is available -- Checking whether header cstddef is available - yes -- Checking whether stl string has operator!= for char* -- Checking whether stl string has operator!= for char* - yes -- Checking whether stl has iterator_traits -- Checking whether stl has iterator_traits - yes -- Checking whether stl has standard template allocator -- Checking whether stl has standard template allocator - yes -- Checking for rebind member of stl allocator -- Checking for rebind member of stl allocator - yes -- Checking for non-standard argument to stl allocator<>::max_size -- Checking for non-standard argument to stl allocator<>::max_size - no -- Checking whether stl containers support allocator objects. -- Checking whether stl containers support allocator objects. - yes -- Checking whether ios has binary openmode -- Checking whether ios has binary openmode - yes -- Checking whether "<>" is needed for template friends -- Checking whether "<>" is needed for template friends - ye
Re: [CMake] CPack and RPM packages
On Tue, Mar 8, 2011 at 12:45 AM, Eric Noulard wrote: > 2011/3/8 Laszlo Papp : >> Well: http://public.kitware.com/Bug/view.php?id=11595 >> That is fixed in cmake 2.8.4. >> Changelog: http://www.cmake.org/pipermail/cmake/2011-February/042839.html >> "CPackRPM fix bug 0011595 : Can't generate RPMs (on FC11...)" >> >> I am trying to build this version now on MeeGo since the available >> binary one is 2.8.3. But if it is fixed in 2.8.4, I wonder why you did >> not know it ? > > I do know this bug, I fixed it. > > I'm just a mere human being and I did not recognize your symptom > as being the same as the refered bug. > > I am really sorry for the wasted time, yours and mine :-/. No idea whether or not that will be the solution, but It is hilarious, I cannot run the cmake ../ properly on the version 2.8.4... I mean it always enters an "endless loop" at random point, but all the time. I heard qemu+cmake is scary, but still How can I build the newest version of the cmake ? Cmake freezes all the time from the shadow build directory It is more than quite /pesky/. Best Regards, Laszlo Papp ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
2011/3/8 Laszlo Papp : > Well: http://public.kitware.com/Bug/view.php?id=11595 > That is fixed in cmake 2.8.4. > Changelog: http://www.cmake.org/pipermail/cmake/2011-February/042839.html > "CPackRPM fix bug 0011595 : Can't generate RPMs (on FC11...)" > > I am trying to build this version now on MeeGo since the available > binary one is 2.8.3. But if it is fixed in 2.8.4, I wonder why you did > not know it ? I do know this bug, I fixed it. I'm just a mere human being and I did not recognize your symptom as being the same as the refered bug. I am really sorry for the wasted time, yours and mine :-/. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
Well: http://public.kitware.com/Bug/view.php?id=11595 That is fixed in cmake 2.8.4. Changelog: http://www.cmake.org/pipermail/cmake/2011-February/042839.html "CPackRPM fix bug 0011595 : Can't generate RPMs (on FC11...)" I am trying to build this version now on MeeGo since the available binary one is 2.8.3. But if it is fixed in 2.8.4, I wonder why you did not know it ? Best Regards, Laszlo Papp On Tue, Mar 8, 2011 at 12:31 AM, Eric Noulard wrote: > 2011/3/7 Laszlo Papp : >> As said, the working OBS spec files can be found here: >> http://repo.pub.meego.com/home:/sandst1/standard/armv7l/ >> http://repo.pub.meego.com/home:/sandst1/standard/i586/ > > Not really, since binary RPMs do not contains the spec file, > but I did find the spec file in src: > http://repo.pub.meego.com/home:/sandst1/standard/src/ > > (within the src.rpm) > >> http://djszapi.homelinux.net/gluon.spec -> this is the cpack/cmake >> generated one. > > I have seen that one, and as I said many > files seems to be installed with ABSOLUTE DESTINATION and > end-up with a %config attribute. > > If they were installed with relative PATH this wouldn't be the case. > >> Well, the cpack one doesn't really do anything, it only moves files >> around (and apparently requires some external calling code to move >> them into place). > > CPackRPM supposed CMake+build has already been run > so CPackRPM generated spec file is a "shortcutted one". > >> I don't know anything about cpack, just that the spec file you have >> there doesn't do anything except moving files around (and maybe >> package them if they happen to end up in the right place), but >> certianly not build anything. > > Yes that's the expected behavior. > You cannot (in your case) call CPack without calling CMake first. > CMake + make will do the build before CPack get a chance to run. > > > -- > Erk > Membre de l'April - « promouvoir et défendre le logiciel libre » - > http://www.april.org > ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
2011/3/7 Laszlo Papp : > As said, the working OBS spec files can be found here: > http://repo.pub.meego.com/home:/sandst1/standard/armv7l/ > http://repo.pub.meego.com/home:/sandst1/standard/i586/ Not really, since binary RPMs do not contains the spec file, but I did find the spec file in src: http://repo.pub.meego.com/home:/sandst1/standard/src/ (within the src.rpm) > http://djszapi.homelinux.net/gluon.spec -> this is the cpack/cmake > generated one. I have seen that one, and as I said many files seems to be installed with ABSOLUTE DESTINATION and end-up with a %config attribute. If they were installed with relative PATH this wouldn't be the case. > Well, the cpack one doesn't really do anything, it only moves files > around (and apparently requires some external calling code to move > them into place). CPackRPM supposed CMake+build has already been run so CPackRPM generated spec file is a "shortcutted one". > I don't know anything about cpack, just that the spec file you have > there doesn't do anything except moving files around (and maybe > package them if they happen to end up in the right place), but > certianly not build anything. Yes that's the expected behavior. You cannot (in your case) call CPack without calling CMake first. CMake + make will do the build before CPack get a chance to run. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
Further news, I have just tried the rpm generation on my host system out and it worked like a charm, here are the logs: http://djszapi.homelinux.net/cpack_host.log http://djszapi.homelinux.net/gluon_host.spec I hope it helps with something... Best Regards, Laszlo Papp On Mon, Mar 7, 2011 at 9:29 PM, Laszlo Papp wrote: > As said, the working OBS spec files can be found here: > http://repo.pub.meego.com/home:/sandst1/standard/armv7l/ > http://repo.pub.meego.com/home:/sandst1/standard/i586/ > > http://djszapi.homelinux.net/gluon.spec -> this is the cpack/cmake > generated one. > > Well, the cpack one doesn't really do anything, it only moves files > around (and apparently requires some external calling code to move > them into place). > I don't know anything about cpack, just that the spec file you have > there doesn't do anything except moving files around (and maybe > package them if they happen to end up in the right place), but > certianly not build anything. > > Best Regards, > Laszlo Papp > > On Mon, Mar 7, 2011 at 9:16 PM, Laszlo Papp wrote: >> On Mon, Mar 7, 2011 at 9:11 PM, Eric Noulard wrote: >>> 2011/3/7 Laszlo Papp : Any progress on it ? >>> >>> Nope. >>> I won't be very responsive this week. >> >> That does not sound too good.. ! >> One more information, this n900-devel image uses internally qemu and I am not sure that can cause any issue for the build system. >>> >>> I don't like I said I'm not that experienced with cross-compiling env. >> >> Nobody told you are, I have been just trying to provide as much >> information as I can ... >> That is also interesting why the debian packaging worked just fine in the scratchbox using also qemu internally. >>> >>> Does the pb you are facing for RPM occur in the same scractchbox env? >> >> No, maemo/debian system (scratchbox) is a different story compared to >> the meego/rpm way. >> >>> If this repo corresponds to the same gluon: >>> http://gitorious.org/gluon/gluon/blobs/master/core/CMakeLists.txt >> >> No, it does not, and it is also mentioned on the main site by the >> kde-sysadmins so that do not use it because it is quite obsolete. It >> is a gitorious tragedy we cannot remove that from there. >> >> This is the current repository: >> https://projects.kde.org/projects/playground/games/gluon/repository >> >> Best Regards, >> Laszlo Papp >> > ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
As said, the working OBS spec files can be found here: http://repo.pub.meego.com/home:/sandst1/standard/armv7l/ http://repo.pub.meego.com/home:/sandst1/standard/i586/ http://djszapi.homelinux.net/gluon.spec -> this is the cpack/cmake generated one. Well, the cpack one doesn't really do anything, it only moves files around (and apparently requires some external calling code to move them into place). I don't know anything about cpack, just that the spec file you have there doesn't do anything except moving files around (and maybe package them if they happen to end up in the right place), but certianly not build anything. Best Regards, Laszlo Papp On Mon, Mar 7, 2011 at 9:16 PM, Laszlo Papp wrote: > On Mon, Mar 7, 2011 at 9:11 PM, Eric Noulard wrote: >> 2011/3/7 Laszlo Papp : >>> Any progress on it ? >> >> Nope. >> I won't be very responsive this week. > > That does not sound too good.. ! > >>> One more information, this n900-devel image uses >>> internally qemu and I am not sure that can cause any issue for the >>> build system. >> >> I don't like I said I'm not that experienced with cross-compiling env. > > Nobody told you are, I have been just trying to provide as much > information as I can ... > >>> That is also interesting why the debian packaging worked just fine in >>> the scratchbox using also qemu internally. >> >> Does the pb you are facing for RPM occur in the same scractchbox env? > > No, maemo/debian system (scratchbox) is a different story compared to > the meego/rpm way. > >> If this repo corresponds to the same gluon: >> http://gitorious.org/gluon/gluon/blobs/master/core/CMakeLists.txt > > No, it does not, and it is also mentioned on the main site by the > kde-sysadmins so that do not use it because it is quite obsolete. It > is a gitorious tragedy we cannot remove that from there. > > This is the current repository: > https://projects.kde.org/projects/playground/games/gluon/repository > > Best Regards, > Laszlo Papp > ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
On Mon, Mar 7, 2011 at 9:11 PM, Eric Noulard wrote: > 2011/3/7 Laszlo Papp : >> Any progress on it ? > > Nope. > I won't be very responsive this week. That does not sound too good.. ! >> One more information, this n900-devel image uses >> internally qemu and I am not sure that can cause any issue for the >> build system. > > I don't like I said I'm not that experienced with cross-compiling env. Nobody told you are, I have been just trying to provide as much information as I can ... >> That is also interesting why the debian packaging worked just fine in >> the scratchbox using also qemu internally. > > Does the pb you are facing for RPM occur in the same scractchbox env? No, maemo/debian system (scratchbox) is a different story compared to the meego/rpm way. > If this repo corresponds to the same gluon: > http://gitorious.org/gluon/gluon/blobs/master/core/CMakeLists.txt No, it does not, and it is also mentioned on the main site by the kde-sysadmins so that do not use it because it is quite obsolete. It is a gitorious tragedy we cannot remove that from there. This is the current repository: https://projects.kde.org/projects/playground/games/gluon/repository Best Regards, Laszlo Papp ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
2011/3/7 Laszlo Papp :
> Any progress on it ?
Nope.
I won't be very responsive this week.
> One more information, this n900-devel image uses
> internally qemu and I am not sure that can cause any issue for the
> build system.
I don't like I said I'm not that experienced with cross-compiling env.
> That is also interesting why the debian packaging worked just fine in
> the scratchbox using also qemu internally.
Does the pb you are facing for RPM occur in the same scractchbox env?
If this repo corresponds to the same gluon:
http://gitorious.org/gluon/gluon/blobs/master/core/CMakeLists.txt
then those:
set(INCLUDE_INSTALL_DIR ${CMAKE_INSTALL_PREFIX}/include
CACHE PATH "The subdirectory relative to the install prefix where
header files will be installed.")
set(LIB_INSTALL_DIR ${CMAKE_INSTALL_PREFIX}/lib${LIB_SUFFIX}
CACHE PATH "The subdirectory relative to the install prefix where
libraries will be installed.")
set(SHARE_INSTALL_DIR ${CMAKE_INSTALL_PREFIX}/share
CACHE PATH "The subdiractory relative to the install prefix where
data and other files will be installed.")
are not a good idea because after that you use _INSTALL_DIR as
DESTINATIOn of your
INSTALL(...) command which makes it use an ABSOLUTE_INSTALL PATH.
you shouldn't use " ${CMAKE_INSTALL_PREFIX}/share " but "share" which
would make it a relative path.
Is there any reason you use absolute destination path.
(this is probably not the culprit but this doesn't help either).
I'll try to examine the problem more in detail tomorrow.
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
Any progress on it ? One more information, this n900-devel image uses internally qemu and I am not sure that can cause any issue for the build system. That is also interesting why the debian packaging worked just fine in the scratchbox using also qemu internally. Best Regards, Laszlo Papp On Mon, Mar 7, 2011 at 5:27 AM, Laszlo Papp wrote: > By the way, you can find here the gluon-*.rpm packages built by the OBS: > http://repo.pub.meego.com/home:/sandst1/standard/armv7l/ > http://repo.pub.meego.com/home:/sandst1/standard/i586/ > (unpack it with rpm2cpio | cpio -idmv) > > Those spec files are done by a packager (human), thus not automated by > a generator. I am not sure it helps with anything after all, but I try > to provide as much as I can. > > Best Regards, > Laszlo Papp > > On Mon, Mar 7, 2011 at 2:33 AM, Laszlo Papp wrote: >> On Sun, Mar 6, 2011 at 11:27 PM, Eric Noulard wrote: >>> 2011/3/6 Laszlo Papp : Mmh, my previous mail is blocked because the cpack.log is too big. http://djszapi.homelinux.net/rpmbuild.out http://djszapi.homelinux.net/rpmbuild.err http://djszapi.homelinux.net/cpack.log >>> >>> I do not quite understand what makes rpmbuild fail. >>> Could you send me [a link to] the generated "gluon.spec" file. >>> >>> And could you show what are the INSTALL rules you use in the CMakeLists.txt >>> for >>> gluon_qtplayer >>> and >>> template.qml >>> >>> and >>> Invaders_Assets_Material.gml >> >> http://djszapi.homelinux.net/gluon.spec >> http://djszapi.homelinux.net/template.qml.install >> http://djszapi.homelinux.net/qtplayer.install >> http://djszapi.homelinux.net/invaders_assets_material.gml.install => >> "/usr/share/gluon/games/invaders.gluon/Assets/Invaders_Assets_Material.gml" >> => under the invaders.gluon >> >> Best Regards, >> Laszlo Papp >> > ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
By the way, you can find here the gluon-*.rpm packages built by the OBS: http://repo.pub.meego.com/home:/sandst1/standard/armv7l/ http://repo.pub.meego.com/home:/sandst1/standard/i586/ (unpack it with rpm2cpio | cpio -idmv) Those spec files are done by a packager (human), thus not automated by a generator. I am not sure it helps with anything after all, but I try to provide as much as I can. Best Regards, Laszlo Papp On Mon, Mar 7, 2011 at 2:33 AM, Laszlo Papp wrote: > On Sun, Mar 6, 2011 at 11:27 PM, Eric Noulard wrote: >> 2011/3/6 Laszlo Papp : >>> Mmh, my previous mail is blocked because the cpack.log is too big. >>> >>> http://djszapi.homelinux.net/rpmbuild.out >>> http://djszapi.homelinux.net/rpmbuild.err >>> http://djszapi.homelinux.net/cpack.log >> >> I do not quite understand what makes rpmbuild fail. >> Could you send me [a link to] the generated "gluon.spec" file. >> >> And could you show what are the INSTALL rules you use in the CMakeLists.txt >> for >> gluon_qtplayer >> and >> template.qml >> >> and >> Invaders_Assets_Material.gml > > http://djszapi.homelinux.net/gluon.spec > http://djszapi.homelinux.net/template.qml.install > http://djszapi.homelinux.net/qtplayer.install > http://djszapi.homelinux.net/invaders_assets_material.gml.install => > "/usr/share/gluon/games/invaders.gluon/Assets/Invaders_Assets_Material.gml" > => under the invaders.gluon > > Best Regards, > Laszlo Papp > ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
On Sun, Mar 6, 2011 at 11:27 PM, Eric Noulard wrote: > 2011/3/6 Laszlo Papp : >> Mmh, my previous mail is blocked because the cpack.log is too big. >> >> http://djszapi.homelinux.net/rpmbuild.out >> http://djszapi.homelinux.net/rpmbuild.err >> http://djszapi.homelinux.net/cpack.log > > I do not quite understand what makes rpmbuild fail. > Could you send me [a link to] the generated "gluon.spec" file. > > And could you show what are the INSTALL rules you use in the CMakeLists.txt > for > gluon_qtplayer > and > template.qml > > and > Invaders_Assets_Material.gml http://djszapi.homelinux.net/gluon.spec http://djszapi.homelinux.net/template.qml.install http://djszapi.homelinux.net/qtplayer.install http://djszapi.homelinux.net/invaders_assets_material.gml.install => "/usr/share/gluon/games/invaders.gluon/Assets/Invaders_Assets_Material.gml" => under the invaders.gluon Best Regards, Laszlo Papp ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
2011/3/6 Laszlo Papp : > Mmh, my previous mail is blocked because the cpack.log is too big. > > http://djszapi.homelinux.net/rpmbuild.out > http://djszapi.homelinux.net/rpmbuild.err > http://djszapi.homelinux.net/cpack.log I do not quite understand what makes rpmbuild fail. Could you send me [a link to] the generated "gluon.spec" file. And could you show what are the INSTALL rules you use in the CMakeLists.txt for gluon_qtplayer and template.qml and Invaders_Assets_Material.gml -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
Mmh, my previous mail is blocked because the cpack.log is too big.
http://djszapi.homelinux.net/rpmbuild.out
http://djszapi.homelinux.net/rpmbuild.err
http://djszapi.homelinux.net/cpack.log
Best Regards,
Laszlo Papp
On Sun, Mar 6, 2011 at 9:43 PM, Laszlo Papp wrote:
> On Sun, Mar 6, 2011 at 9:34 PM, Eric Noulard wrote:
>> 2011/3/6 Laszlo Papp :
>>> Hi,
>>>
>>> I do not get the infinite loop right now (not sure what caused it
>>> then), but I get an error while trying.
>>>
>>> djszapi@djszapi:/home/meego/gluon/buildroot /home/meego/gluon/build # cpack
>>> CPack: Create package using RPM
>>> CPack: Install projects
>>> CPack: - Run preinstall target for: Gluon
>>> CPack: - Install project: Gluon
>>> CPack: Create package
>>> CPackRPM: Will use GENERATED spec file:
>>> /home/meego/gluon/build/_CPack_Packages/Linux/RPM/SPECS/gluon.spec
>>> CPack Error: Problem copying the package:
>>> /home/meego/gluon/build/_CPack_Packages/Linux/RPM/Gluon-0.71.0.rpm to
>>> /home/meego/gluon/build/Gluon-0.71.0.rpm
>>> CPack Error: Error when generating package: Gluon
>>> djszapi@djszapi:/home/meego/gluon/buildroot /home/meego/gluon/build #
>>>
>>> The file is definitely not there, yes :o
>>>
>>> http://www.mail-archive.com/cmake@cmake.org/msg20169.html
>>>
>>> I have tried the aforementioned thread so that to add the
>>> set(CPACK_SET_DESTDIR ON), but it ended up by printing this message:
>>> CPackRPM:Warning: CPACK_SET_DESTDIR is set (=ON) while requesting a
>>> relocatable package (CPACK_RPM_PACKAGE_RELOCATABLE is set): this is
>>> not supported, the package won't be relocatable.
>>
>> Yes that's normal warning, since 2.8.3 you don't need to set
>> CPACK_SET_DESTDIR to ON for either RPM or DEB
>> the generator should handle that just fine without.
>>
>> RPM is even trying to make the package relocatable
>> (installable with a configurable prefix) but it cannot do it
>> with CPACK_SET_DESTDIR to ON.
>>
>>
>>>
>>> This is the relevant CPACK section in my CMakeLists.txt:
>>> #Packaging options
>>> #common package generation settings
>>> set(CPACK_PACKAGE_DESCRIPTION_SUMMARY "An open framework to create,
>>> distribute and play games")
>>> set(CPACK_PACKAGE_NAME "Gluon")
>>> set(CPACK_PACKAGE_VERSION
>>> "${GLUON_VERSION_MAJOR}.${GLUON_VERSION_MINOR}.${GLUON_VERSION_PATCH}")
>>> set(CPACK_PACKAGE_FILE_NAME "Gluon-${GLUON_VERSION_STRING}")
>>> set(CPACK_GENERATOR "RPM;TGZ")
>>> set(CPACK_SET_DESTDIR ON) # this is the line I played off, but seems
>>> not the culsprit.
>>
>> Yes don't set it.
>
> Okay.
>
>>> set(CPACK_PACKAGE_CONTACT "Laszlo Papp , Arjen
>>> Hiemstra ")
>>>
>>> #debian package generation
>>> #set(CPACK_DEBIAN_PACKAGE_DEPENDS "libqt4-gui (>= 4.6), libqt4-opengl
>>> (>= 4.6), libopenal1, libsndfile1, libvorbis0a, libgles2")
>>> #set(CPACK_DEBIAN_PACKAGE_SECTION "Games")
>>>
>>> #rpm package generation
>>>
>>> include(InstallRequiredSystemLibraries)
>>> include(CPack)
>>
>> Try running cpack with the following command line
>>
>> cpack --verbose --debug -D CPACK_RPM_PACKAGE_DEBUG=1 -G RPM
>>
>> and send me the output + rpmbuild.out and rpmbuild.err files
>> (you'll see where to find those in the trace).
>
> I have just attached them. Thank you in advance!
>
> Best Regards,
> Laszlo Papp
>
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
2011/3/6 Laszlo Papp :
> Hi,
>
> I do not get the infinite loop right now (not sure what caused it
> then), but I get an error while trying.
>
> djszapi@djszapi:/home/meego/gluon/buildroot /home/meego/gluon/build # cpack
> CPack: Create package using RPM
> CPack: Install projects
> CPack: - Run preinstall target for: Gluon
> CPack: - Install project: Gluon
> CPack: Create package
> CPackRPM: Will use GENERATED spec file:
> /home/meego/gluon/build/_CPack_Packages/Linux/RPM/SPECS/gluon.spec
> CPack Error: Problem copying the package:
> /home/meego/gluon/build/_CPack_Packages/Linux/RPM/Gluon-0.71.0.rpm to
> /home/meego/gluon/build/Gluon-0.71.0.rpm
> CPack Error: Error when generating package: Gluon
> djszapi@djszapi:/home/meego/gluon/buildroot /home/meego/gluon/build #
>
> The file is definitely not there, yes :o
>
> http://www.mail-archive.com/cmake@cmake.org/msg20169.html
>
> I have tried the aforementioned thread so that to add the
> set(CPACK_SET_DESTDIR ON), but it ended up by printing this message:
> CPackRPM:Warning: CPACK_SET_DESTDIR is set (=ON) while requesting a
> relocatable package (CPACK_RPM_PACKAGE_RELOCATABLE is set): this is
> not supported, the package won't be relocatable.
Yes that's normal warning, since 2.8.3 you don't need to set
CPACK_SET_DESTDIR to ON for either RPM or DEB
the generator should handle that just fine without.
RPM is even trying to make the package relocatable
(installable with a configurable prefix) but it cannot do it
with CPACK_SET_DESTDIR to ON.
>
> This is the relevant CPACK section in my CMakeLists.txt:
> #Packaging options
> #common package generation settings
> set(CPACK_PACKAGE_DESCRIPTION_SUMMARY "An open framework to create,
> distribute and play games")
> set(CPACK_PACKAGE_NAME "Gluon")
> set(CPACK_PACKAGE_VERSION
> "${GLUON_VERSION_MAJOR}.${GLUON_VERSION_MINOR}.${GLUON_VERSION_PATCH}")
> set(CPACK_PACKAGE_FILE_NAME "Gluon-${GLUON_VERSION_STRING}")
> set(CPACK_GENERATOR "RPM;TGZ")
> set(CPACK_SET_DESTDIR ON) # this is the line I played off, but seems
> not the culsprit.
Yes don't set it.
> set(CPACK_PACKAGE_CONTACT "Laszlo Papp , Arjen
> Hiemstra ")
>
> #debian package generation
> #set(CPACK_DEBIAN_PACKAGE_DEPENDS "libqt4-gui (>= 4.6), libqt4-opengl
> (>= 4.6), libopenal1, libsndfile1, libvorbis0a, libgles2")
> #set(CPACK_DEBIAN_PACKAGE_SECTION "Games")
>
> #rpm package generation
>
> include(InstallRequiredSystemLibraries)
> include(CPack)
Try running cpack with the following command line
cpack --verbose --debug -D CPACK_RPM_PACKAGE_DEBUG=1 -G RPM
and send me the output + rpmbuild.out and rpmbuild.err files
(you'll see where to find those in the trace).
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
Hi,
I do not get the infinite loop right now (not sure what caused it
then), but I get an error while trying.
djszapi@djszapi:/home/meego/gluon/buildroot /home/meego/gluon/build # cpack
CPack: Create package using RPM
CPack: Install projects
CPack: - Run preinstall target for: Gluon
CPack: - Install project: Gluon
CPack: Create package
CPackRPM: Will use GENERATED spec file:
/home/meego/gluon/build/_CPack_Packages/Linux/RPM/SPECS/gluon.spec
CPack Error: Problem copying the package:
/home/meego/gluon/build/_CPack_Packages/Linux/RPM/Gluon-0.71.0.rpm to
/home/meego/gluon/build/Gluon-0.71.0.rpm
CPack Error: Error when generating package: Gluon
djszapi@djszapi:/home/meego/gluon/buildroot /home/meego/gluon/build #
The file is definitely not there, yes :o
http://www.mail-archive.com/cmake@cmake.org/msg20169.html
I have tried the aforementioned thread so that to add the
set(CPACK_SET_DESTDIR ON), but it ended up by printing this message:
CPackRPM:Warning: CPACK_SET_DESTDIR is set (=ON) while requesting a
relocatable package (CPACK_RPM_PACKAGE_RELOCATABLE is set): this is
not supported, the package won't be relocatable.
This is the relevant CPACK section in my CMakeLists.txt:
#Packaging options
#common package generation settings
set(CPACK_PACKAGE_DESCRIPTION_SUMMARY "An open framework to create,
distribute and play games")
set(CPACK_PACKAGE_NAME "Gluon")
set(CPACK_PACKAGE_VERSION
"${GLUON_VERSION_MAJOR}.${GLUON_VERSION_MINOR}.${GLUON_VERSION_PATCH}")
set(CPACK_PACKAGE_FILE_NAME "Gluon-${GLUON_VERSION_STRING}")
set(CPACK_GENERATOR "RPM;TGZ")
set(CPACK_SET_DESTDIR ON) # this is the line I played off, but seems
not the culsprit.
set(CPACK_PACKAGE_CONTACT "Laszlo Papp , Arjen
Hiemstra ")
#debian package generation
#set(CPACK_DEBIAN_PACKAGE_DEPENDS "libqt4-gui (>= 4.6), libqt4-opengl
(>= 4.6), libopenal1, libsndfile1, libvorbis0a, libgles2")
#set(CPACK_DEBIAN_PACKAGE_SECTION "Games")
#rpm package generation
include(InstallRequiredSystemLibraries)
include(CPack)
Best Regards,
Laszlo Papp
On Sun, Mar 6, 2011 at 7:47 PM, Eric Noulard wrote:
> 2011/3/6 Laszlo Papp :
>> CPack froze for hours What happened ? Seems a "nice" infinite loop...
>> Idea ?
>>
>> Best Regards,
>> Laszlo Papp
>>
>> cpack
>> CPack: Create package using RPM
>> CPack: Install projects
>> CPack: - Run preinstall target for: Gluon
>
> try with verbose/debug mode:
>
> cpack --verbose
> or
> cpack --debug
> or
> both
> cpack --verbose --debug
>
> For CPackRPM you can have some more informations with
>
> cpack -D CPACK_RPM_PACKAGE_DEBUG=1 --verbose --debug
>
> Then send me the log.
> --
> Erk
> Membre de l'April - « promouvoir et défendre le logiciel libre » -
> http://www.april.org
>
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
2011/3/6 Laszlo Papp : > CPack froze for hours What happened ? Seems a "nice" infinite loop... > Idea ? > > Best Regards, > Laszlo Papp > > cpack > CPack: Create package using RPM > CPack: Install projects > CPack: - Run preinstall target for: Gluon try with verbose/debug mode: cpack --verbose or cpack --debug or both cpack --verbose --debug For CPackRPM you can have some more informations with cpack -D CPACK_RPM_PACKAGE_DEBUG=1 --verbose --debug Then send me the log. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
CPack froze for hours What happened ? Seems a "nice" infinite loop... Idea ? Best Regards, Laszlo Papp cpack CPack: Create package using RPM CPack: Install projects CPack: - Run preinstall target for: Gluon ^[[D ^C On Sun, Mar 6, 2011 at 11:52 AM, Eric Noulard wrote: > 2011/3/5 Laszlo Papp : >> On Sat, Mar 5, 2011 at 5:32 PM, Eric Noulard wrote: >>> 2011/3/5 Laszlo Papp : Well, first I cannot build :) >>> >>> I thought you were already using CPack for Deb package? >>> >>> If you never used a cross-compiling setup with CMake then >>> read this first: >>> http://www.cmake.org/Wiki/CMake_Cross_Compiling >> >> Meanwhile it can solves the problem, I think there should a developer >> awareless solution. Can you solve it in a smarter way in the future, >> please ? > > Unfortunately I won't have time to work on tis now. > Moreover I don't have very much experience in cross-compiling env. > so it would take me some to it reasonable. > > I let other CMake developers comment on that but I think > "proper" cross-compiling setup with CMake goes far further than > giving the compiler some -march argument. > It may work for very simple CMakeLists.txt but would probably break > as soon as you use some CMake features (find modules, try_compile etc...) > > That said may be providing the proper CMake toolchain file(s) may be more > the work of Meego environment provider than CMake itself. > > I am not refusing to help but I do not have time to handle that now. > If you want you can file a bug report > http://public.kitware.com/Bug/bug_report_page.php > explaining that you want to do "cross-packaging" with cpack, > I'll put the report in the backlog and come back to the issue when > more spare time re-appear. > > > -- > Erk > Membre de l'April - « promouvoir et défendre le logiciel libre » - > http://www.april.org > ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
2011/3/5 Laszlo Papp : > On Sat, Mar 5, 2011 at 5:32 PM, Eric Noulard wrote: >> 2011/3/5 Laszlo Papp : >>> Well, first I cannot build :) >> >> I thought you were already using CPack for Deb package? >> >> If you never used a cross-compiling setup with CMake then >> read this first: >> http://www.cmake.org/Wiki/CMake_Cross_Compiling > > Meanwhile it can solves the problem, I think there should a developer > awareless solution. Can you solve it in a smarter way in the future, > please ? Unfortunately I won't have time to work on tis now. Moreover I don't have very much experience in cross-compiling env. so it would take me some to it reasonable. I let other CMake developers comment on that but I think "proper" cross-compiling setup with CMake goes far further than giving the compiler some -march argument. It may work for very simple CMakeLists.txt but would probably break as soon as you use some CMake features (find modules, try_compile etc...) That said may be providing the proper CMake toolchain file(s) may be more the work of Meego environment provider than CMake itself. I am not refusing to help but I do not have time to handle that now. If you want you can file a bug report http://public.kitware.com/Bug/bug_report_page.php explaining that you want to do "cross-packaging" with cpack, I'll put the report in the backlog and come back to the issue when more spare time re-appear. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
On Sat, Mar 5, 2011 at 5:32 PM, Eric Noulard wrote: > 2011/3/5 Laszlo Papp : >> Well, first I cannot build :) > > I thought you were already using CPack for Deb package? Yes, but from scratchbox and scratchbox passed the corrent toolchain arguments... By the way, I solved it with export CXXFLAGS in my ~/.bashrc file for now, thus I do not need this toolchain file right now. Best Regards, Laszlo Papp ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
On Sat, Mar 5, 2011 at 5:32 PM, Eric Noulard wrote: > 2011/3/5 Laszlo Papp : >> Well, first I cannot build :) > > I thought you were already using CPack for Deb package? > > If you never used a cross-compiling setup with CMake then > read this first: > http://www.cmake.org/Wiki/CMake_Cross_Compiling Meanwhile it can solves the problem, I think there should a developer awareless solution. Can you solve it in a smarter way in the future, please ? We have just discussed it on the #meego channel: 19:05 < thiago> djszapi: tell cmake to pass the -march=armv7-a flag to the compiler 19:05 < thiago> that's your answer 19:05 < djszapi> carstenek: also it was not fair sometimes on #meego.fi either. 19:05 -!- JPohlmann [~jannis@xfce/core-developer/JPohlmann] has joined #meego 19:05 -!- seg [~r...@75-63-28-213.lightspeed.irvnca.sbcglobal.net] has quit [Quit: Leaving] 19:05 < djszapi> thiago: yeah, toolchain file... 19:05 < djszapi> but the problem is that all the developers should aware of that. 19:05 < thiago> yes 19:05 < thiago> which means it's a toolchain problem 19:06 < djszapi> still not handy like in case sb :p 19:06 < thiago> or, more to the point: Qt has hardcoded instructions to use ARMv6 instructions 19:06 < thiago> qmake is configured to know to pass the flag 19:06 < thiago> everything else that uses Qt needs to know that too 19:07 < djszapi> yes, but I would be more glad about hiding it from the developer :o 19:07 < thiago> so teach cmake to extract the info from qmake and use it 19:08 < djszapi> so propose something to the cmake developers. 19:08 < thiago> yes, you should propose something to them Best Regards, Laszlo Papp ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
2011/3/5 Laszlo Papp : > Well, first I cannot build :) I thought you were already using CPack for Deb package? If you never used a cross-compiling setup with CMake then read this first: http://www.cmake.org/Wiki/CMake_Cross_Compiling [...] -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] CPack and RPM packages
Restore the mailing list !
Well, first I cannot build :)
cd /home/meego/gluon/build/core && /usr/bin/c++
-DMAKE_GLUON_CORE_LIB -Wall -Wno-psabi -Wall -g3 -ggdb -O0 -Wno-psabi
-fPIC -I/home/meego/gluon -I/home/meego/gluon/build
-I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative
-I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtDBus
-I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql
-I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtNetwork
-I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtHelp
-I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest
-I/usr/include/qt4/QtScript -I/usr/include/qt4/QtSvg
-I/usr/include/qt4/QtGui -I/usr/share/qt4/mkspecs/default
-I/usr/include/qt4 -I/usr/include/qt4/QtCore
-I/home/meego/gluon/build/core -I/home/meego/gluon/core -o
CMakeFiles/GluonCore.dir/debughelper.cpp.o -c
/home/meego/gluon/core/debughelper.cpp
/tmp/cc9jVmy7.s: Assembler messages:
/tmp/cc9jVmy7.s:8659: Error: selected processor does not support `ldrex r4,[r3]'
/tmp/cc9jVmy7.s:8661: Error: selected processor does not support
`strex r5,r4,[r3]'
/tmp/cc9jVmy7.s:8711: Error: selected processor does not support `ldrex r4,[r3]'
/tmp/cc9jVmy7.s:8713: Error: selected processor does not support
`strex r5,r4,[r3]'
make[2]: *** [core/CMakeFiles/GluonCore.dir/debughelper.cpp.o] Error 1
make[2]: Leaving directory `/home/meego/gluon/build'
make[1]: *** [core/CMakeFiles/GluonCore.dir/all] Error 2
make[1]: Leaving directory `/home/meego/gluon/build'
make: *** [all] Error 2
I have been said by Thiago, it is because of the missing
-march=armv7-a option. It should be handled internally by cmake, can
you fix this bug, please and tell me the hackaround that I can use
until the release ?
Thank you in advance!
Best Regards,
Laszlo Papp
On Fri, Mar 4, 2011 at 9:50 PM, Eric Noulard wrote:
> 2011/3/4 Laszlo Papp :
>> On Fri, Mar 4, 2011 at 3:05 PM, Eric Noulard wrote:
>>> 2011/3/4 Laszlo Papp :
Hi,
Can I create an rpm package with cpack in order to not deal with spec
files ?
>>>
>>> Yes you can CPackRPM is meant to do that:
>>> http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#RPM_.28Unix_Only.29
>>>
>>> The fastest path is to try:
>>>
>>> $ cd /path/to/builddir
>>> $ cpack -G RPM
>>
>> Right, so you are saying it will create the rpm package with no spec
>> file reuqested.
>
> Yes.
> CPackRPM required some CPACK_RPM_ var def,
> however most of them have default values.
>
> The following command will give you the list:
>
> $ cmake --help-module CPackRPM | grep -B 1 -A 1 "Mandatory : YES"
>
We did not need to put any debian/{changelog,rules,control} files
related implementation into the project so that to build a debian
package for arm with cpack.
>>>
>>> However are you cross-compiling to arm or do you package natively on
>>> arm-linux ?
>>
>> Well not. I am developing on x86_64 in a cross-compilation way for
>> arm, N900, MeeGo.
>> http://wiki.meego.com/Developing_in_a_MeeGo_Environment
>
> I do not know that setup and AFAIK CPackRPM has never been used
> in a cross-compiling env. so like I said before give it a try and
> tell me what happen.
>
>> CPack seems an easier way than OBS if one does not know how to write
>> spec files. That is why I started this whole thread whether or not
>> cpack is an easy way to generate rpm package for the N900 mobile -
>> like previously debian packages with cpack for the same mobile, but
>> Maemo5/Fremantle platform - or I need to make some other further
>> hackery.
>
> Again CPackRPM has been tested in "native" environnement,
> I don't know how it will behave in a chroot ARM Meego image.
>
> Try it, and tell me what happen.
>
PS: I am not on the list, so please drop me into the 'CC' field.
>>>
>>> This is usually a bad habitI am even surprised that you can post
>>> without being on list.
>>> You could subscribe to the list for the duration of your discussion
>>> and then un-subscribe afterwards.
>>
>> I subscribed only for the posting and unsubscribe then immediately
>> since I am not interested in other mails.
>
> Seems awkward to me but OK, that's your choice :-]
>
>
> --
> Erk
> Membre de l'April - « promouvoir et défendre le logiciel libre » -
> http://www.april.org
>
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
2011/3/4 Laszlo Papp :
> On Fri, Mar 4, 2011 at 3:05 PM, Eric Noulard wrote:
>> 2011/3/4 Laszlo Papp :
>>> Hi,
>>>
>>> Can I create an rpm package with cpack in order to not deal with spec files
>>> ?
>>
>> Yes you can CPackRPM is meant to do that:
>> http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#RPM_.28Unix_Only.29
>>
>> The fastest path is to try:
>>
>> $ cd /path/to/builddir
>> $ cpack -G RPM
>
> Right, so you are saying it will create the rpm package with no spec
> file reuqested.
Yes.
CPackRPM required some CPACK_RPM_ var def,
however most of them have default values.
The following command will give you the list:
$ cmake --help-module CPackRPM | grep -B 1 -A 1 "Mandatory : YES"
>>> We did not need to put any debian/{changelog,rules,control} files
>>> related implementation into the project so that to build a debian
>>> package for arm with cpack.
>>
>> However are you cross-compiling to arm or do you package natively on
>> arm-linux ?
>
> Well not. I am developing on x86_64 in a cross-compilation way for
> arm, N900, MeeGo.
> http://wiki.meego.com/Developing_in_a_MeeGo_Environment
I do not know that setup and AFAIK CPackRPM has never been used
in a cross-compiling env. so like I said before give it a try and
tell me what happen.
> CPack seems an easier way than OBS if one does not know how to write
> spec files. That is why I started this whole thread whether or not
> cpack is an easy way to generate rpm package for the N900 mobile -
> like previously debian packages with cpack for the same mobile, but
> Maemo5/Fremantle platform - or I need to make some other further
> hackery.
Again CPackRPM has been tested in "native" environnement,
I don't know how it will behave in a chroot ARM Meego image.
Try it, and tell me what happen.
>>> PS: I am not on the list, so please drop me into the 'CC' field.
>>
>> This is usually a bad habitI am even surprised that you can post
>> without being on list.
>> You could subscribe to the list for the duration of your discussion
>> and then un-subscribe afterwards.
>
> I subscribed only for the posting and unsubscribe then immediately
> since I am not interested in other mails.
Seems awkward to me but OK, that's your choice :-]
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack and RPM packages
2011/3/4 Laszlo Papp :
> Hi,
>
> Can I create an rpm package with cpack in order to not deal with spec files ?
Yes you can CPackRPM is meant to do that:
http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#RPM_.28Unix_Only.29
The fastest path is to try:
$ cd /path/to/builddir
$ cpack -G RPM
> We did not need to put any debian/{changelog,rules,control} files
> related implementation into the project so that to build a debian
> package for arm with cpack.
However are you cross-compiling to arm or do you package natively on arm-linux ?
> https://projects.kde.org/projects/playground/games/gluon/repository/revisions/master/entry/CMakeLists.txt#L162
>
> Can it be done in a similar way to avoid the rpm spec file writing ?
Yes see the doc:
http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#RPM_.28Unix_Only.29
and/or
cmake --help-module CPackRPM
> PS: I am not on the list, so please drop me into the 'CC' field.
This is usually a bad habitI am even surprised that you can post
without being on list.
You could subscribe to the list for the duration of your discussion
and then un-subscribe afterwards.
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] CPack and RPM packages
Hi,
Can I create an rpm package with cpack in order to not deal with spec files ?
We did not need to put any debian/{changelog,rules,control} files
related implementation into the project so that to build a debian
package for arm with cpack.
https://projects.kde.org/projects/playground/games/gluon/repository/revisions/master/entry/CMakeLists.txt#L162
Can it be done in a similar way to avoid the rpm spec file writing ?
Best Regards,
Laszlo Papp
PS: I am not on the list, so please drop me into the 'CC' field.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
