[hugin-ptx] Re: Celeste not compilable
Am Monday 03 August 2009 schrieb Yuval Levy: Markku Kolkka wrote: Like Bruno already explained, the above is the reason why you should never publish packages that install anything _in_ /usr/local. Use /opt if you are really opposed to installing in /usr. I think I start to understand? = Packages for distribution: /usr = Packages for self-use: /usr/local Exactly what I too meant. Yuv Kornel -- Kornel Benko kornel.be...@berlin.de signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Re: Celeste not compilable
Kornel Benko wrote: Am Monday 03 August 2009 schrieb Yuval Levy: So now I have to look into the chrooting as suggested by Roger and then I shall be able to build both 32 and 64 bit versions for whatever version of Debian / Ubuntu on the same box? Yes, but there is a drawback. We have no dependecies listed in the deb-file. I am creating some, but they are specific to _my_ system. I could send you a script to display the dependencies on your system, so we could compare. yes, please. feel free to share your scripts on this list - the more knowledge is spread, the better for the project. Yuv --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Celeste not compilable
Am Monday 03 August 2009 schrieb Yuval Levy: Kornel Benko wrote: Am Monday 03 August 2009 schrieb Yuval Levy: So now I have to look into the chrooting as suggested by Roger and then I shall be able to build both 32 and 64 bit versions for whatever version of Debian / Ubuntu on the same box? Yes, but there is a drawback. We have no dependecies listed in the deb-file. I am creating some, but they are specific to _my_ system. I could send you a script to display the dependencies on your system, so we could compare. yes, please. feel free to share your scripts on this list - the more knowledge is spread, the better for the project. Ok, here it comes. It is poor commented, so some words first. Although it reads dependencies for rpm too, we don't need it, because it looks like rpm itself takes care of it. 1.) Change $packaging from rpm to debian (line 10) 2.) Adapt the $bindir to where you install the package 3.) Install hugin. (e.g. sudo dpkg -i hugin-2009.1.0-Linux.deb) 4.) call getlibs.pl (e.g. perl getlibs.pl) The last output line is what we need. (We have to set the cmake-variable CPACK_DEBIAN_PACKAGE_DEPENDS) Yuv Kornel -- Kornel Benko kornel.be...@berlin.de getlibs.pl Description: Perl program signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Re: Celeste not compilable
Am Sonntag 02 August 2009 schrieb Yuval Levy: Kornel Benko wrote: Am Samstag 01 August 2009 schrieb Yuval Levy: so instead of doing `make install` you do `make package` and then install the package? Exactly. ok, I tried `make package`. The result is a tarball with attached shell script hugin-.00.0-Linux.sh How do I go from there to a .deb file? Here is, how I use it. 1.) cd to svn-src cd /usr/src/hugin/hugin 2.) update sources svn up 3.) cd to the build-directory cd /usr/BUILD/BuildHugin 4.) call cmake and enable debian packages cmake /usr/src/hugin/hugin -DENABLE_LAPACK=YES -DCPACK_BINARY_DEB:BOOL=ON 5.) create package, use the system to keep the processors at work (I have 4) make -j5 package 6.) install it (look for a .deb file in the build-directory. (The version '000.00.0' will hopefully change) sudo dpkg -i hugin-.00.0-Linux.deb ... You may also edit the CMakeCache.txt in the build-directory. Set all CPACK_* but CPACK_BINARY_DEB to OFF, we don't need them. CPACK_BINARY_DEB:BOOL=ON CPACK_BINARY_NSIS:BOOL=OFF CPACK_BINARY_RPM:BOOL=OFF CPACK_BINARY_STGZ:BOOL=OFF CPACK_BINARY_TBZ2:BOOL=OFF CPACK_BINARY_TGZ:BOOL=OFF CPACK_BINARY_TZ:BOOL=OFF ... trunk should not be used to make public packages indeed, I agree with you. That's why I want to branch releases out from trunk and let the release and the trunk move forward in parallel - and packages made public from the branched release codeline. That said, I am creating packages for OpenSuSE 10.3, 64Bit and Ubuntu 9.04, 64Bit. and I guess you are using a script for this? how difficult is it to edit the script to add chrooting and support other versions of Ubuntu and OpenSuSE (32bit, as well as older and newer that are still officially supported)? Yes, I use a script. It is really not too difficult. I've fixed the version in trunk according to the discussion with Bruno. This should fix your process, sorry for the disruption. There is still enough time to discuss details before the next release (although with the locale thing fixed I think it may be a good idea to push a release early. Such visible errors are a pain for users and often result in a lot of bug reports. Let's spare it to them and to us. Thanks, so my remark above, about the version is obsolete. Yuv Kornel -- Kornel Benko kornel.be...@berlin.de signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Re: Celeste not compilable
Am Sonntag 02 August 2009 schrieb Bruno Postle:
On Sat 01-Aug-2009 at 18:21 -0400, Yuval Levy wrote:
In this case, 2.0 is major+minor number and 30801 is the svn-revision.
I think Bruno wanted to keep the patch version. Would a four digit
version number work? major.minor.patch.svn?
hugin-2009.1.0.4138-Linux.deb
Putting the SVN number in the CMakeLists.txt file is a mess, you
change it, commit it and the SVN number changes again.
No, you can 'ask' the svn about the version number.
Like this:
FIND_PROGRAM(_svnversion svnversion)
message(STATUS svnversion = ${_svnversion})
if(NOT ${_svnversion} MATCHES -NOTFOUND)
EXECUTE_PROCESS(COMMAND ${_svnversion} WORKING_DIRECTORY
${TOP_SRC_DIR}
OUTPUT_VARIABLE CPACK_RPM_PACKAGE_RELEASE OUTPUT_STRIP_TRAILING_WHITESPACE)
if(CPACK_RPM_PACKAGE_RELEASE MATCHES ^\([0-9]+\))
set(CPACK_PACKAGE_VERSION_PATCH ${CMAKE_MATCH_1})
endif()
endif()
include(CPack)
Automated packages such as those created by checkinstall or cpack
don't have a fine-grained version. Packaging for distributions
always involves incrementing a 'release; number, putting the svn
number in the name is superfluous.
Hmmm, I am not creating a release :)
1.) I create them to install at /usr/local, which is not the standard
place.
oh, I forgot about those standards. I love the /usr/local way, like in
FreeBSD.
Generally /usr should only contain stuff tracked by the package
manager and /usr/local should only contain stuff manually installed.
This way you can always `rm -rf /usr/local` if it all goes wrong -
Manually deleting or chnaging files from a deb/rpm package is really
going to break stuff.
Kornel
--
Kornel Benko
kornel.be...@berlin.de
signature.asc
Description: This is a digitally signed message part.
[hugin-ptx] Re: Celeste not compilable
Yuval Levy kirjoitti viestissään (lähetysaika sunnuntai, 2. elokuuta 2009): I think we're almost on the same page for this. In FreeBSD /usr is the base system and /usr/local is everything that the user added on top of it, and I like it exactly because you can always `rm -rf /usr/local`. You can't do that any more if any rpm/deb package installs anything in /usr/local or the package management system breaks. (at least rpm does, I don't know the details of dpkg). Hence I would never publish packages that install somewhere else but /usr/local. Like Bruno already explained, the above is the reason why you should never publish packages that install anything _in_ /usr/local. Use /opt if you are really opposed to installing in /usr. -- Markku Kolkka markku.kol...@iki.fi --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Celeste not compilable
Am Freitag 31 Juli 2009 schrieb Bruno Postle: On Sun 26-Jul-2009 at 11:03 -0400, Yuval Levy wrote: Packages are for distribution. No, packages keep track of dependencies, e.g. letting me know when a library change is going to break anything. Packages are also for keeping your system clean, I can switch between any hugin build or uninstall it without trace. +1 Running `make install` on a Linux system is often a really bad idea, especially with untested development software - This is how you break a machine and end-up wiping and reinstalling. Want a package? branch, update the version number in the root CMakeLists.txt No, the version number in the trunk has to be higher than the most recent stable release (or stable branch if this hasn't yet been released). Yes, therefore my version was already patched this way. I regularly create a package. The only one small inconvenience is with rpm-packages. I have to use the --force flag, because the hugin-version never changes. No problems on debian packages. Kornel -- Kornel Benko kornel.be...@berlin.de signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Re: Celeste not compilable
Kornel Benko wrote: Am Freitag 31 Juli 2009 schrieb Bruno Postle: On Sun 26-Jul-2009 at 11:03 -0400, Yuval Levy wrote: Packages are for distribution. No, packages keep track of dependencies, e.g. letting me know when a library change is going to break anything. Packages are also for keeping your system clean, I can switch between any hugin build or uninstall it without trace. +1 so instead of doing `make install` you do `make package` and then install the package? No, the version number in the trunk has to be higher than the most recent stable release (or stable branch if this hasn't yet been released). Yes, therefore my version was already patched this way. I regularly create a package. The only one small inconvenience is with rpm-packages. I have to use the --force flag, because the hugin-version never changes. No problems on debian packages. ok, ok, I got the message that packages need a higher version number and I am sure we can work out a compromise to make everybody happy. You want to be able to package/distribute/install any time and I want to be able to develop any time. No freezes. Parallel rather than sequential. We'll get there together. What would interest me, Kornel, if you are building debian packages and rpm-packages, why are you not distributing them / making them public? Yuv --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Celeste not compilable
Am Samstag 01 August 2009 schrieb Yuval Levy: Kornel Benko wrote: Am Freitag 31 Juli 2009 schrieb Bruno Postle: On Sun 26-Jul-2009 at 11:03 -0400, Yuval Levy wrote: Packages are for distribution. No, packages keep track of dependencies, e.g. letting me know when a library change is going to break anything. Packages are also for keeping your system clean, I can switch between any hugin build or uninstall it without trace. +1 so instead of doing `make install` you do `make package` and then install the package? Exactly. No, the version number in the trunk has to be higher than the most recent stable release (or stable branch if this hasn't yet been released). Yes, therefore my version was already patched this way. I regularly create a package. The only one small inconvenience is with rpm-packages. I have to use the --force flag, because the hugin-version never changes. No problems on debian packages. ok, ok, I got the message that packages need a higher version number and I am sure we can work out a compromise to make everybody happy. You want to be able to package/distribute/install any time and I want to be able to develop any time. No freezes. Parallel rather than sequential. We'll get there together. Maybe something like I created for lyx? Packages there have versions like lyx-2.0.30801-Linux.deb In this case, 2.0 is major+minor number and 30801 is the svn-revision. What would interest me, Kornel, if you are building debian packages and rpm-packages, why are you not distributing them / making them public? Because 1.) I create them to install at /usr/local, which is not the standard place. 2.) I use svn, which is not to be made public packages. I think. That said, I am creating packages for OpenSuSE 10.3, 64Bit and Ubuntu 9.04, 64Bit. Yuv Kornel -- Kornel Benko kornel.be...@berlin.de signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Re: Celeste not compilable
Bruno Postle wrote: Putting the SVN number in the CMakeLists.txt file is a mess, you change it, commit it and the SVN number changes again. OK, forget it. 1.) I create them to install at /usr/local, which is not the standard place. oh, I forgot about those standards. I love the /usr/local way, like in FreeBSD. Generally /usr should only contain stuff tracked by the package manager and /usr/local should only contain stuff manually installed. This way you can always `rm -rf /usr/local` if it all goes wrong - Manually deleting or chnaging files from a deb/rpm package is really going to break stuff. I think we're almost on the same page for this. In FreeBSD /usr is the base system and /usr/local is everything that the user added on top of it, and I like it exactly because you can always `rm -rf /usr/local`. Hence I would never publish packages that install somewhere else but /usr/local. And if Debian or Ubuntu want to make it part of their system, they can install in /usr. Yuv --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Celeste not compilable
On Sun 26-Jul-2009 at 11:03 -0400, Yuval Levy wrote: Packages are for distribution. No, packages keep track of dependencies, e.g. letting me know when a library change is going to break anything. Packages are also for keeping your system clean, I can switch between any hugin build or uninstall it without trace. Running `make install` on a Linux system is often a really bad idea, especially with untested development software - This is how you break a machine and end-up wiping and reinstalling. Want a package? branch, update the version number in the root CMakeLists.txt No, the version number in the trunk has to be higher than the most recent stable release (or stable branch if this hasn't yet been released). -- Bruno --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Celeste not compilable
Am Sonntag 26 Juli 2009 schrieb Yuval Levy:
Kornel Benko wrote:
Hi,
I got this error compiling trunk:
...
/usr/src/hugin/hugin/src/hugin1/hugin/huginApp.cpp: In member function
‘virtual bool huginApp::OnInit()’:
/usr/src/hugin/hugin/src/hugin1/hugin/huginApp.cpp:164: error:
‘LINSTALL_DATA_DIR’ was not declared in this scope
...
With attached patch it compiles again.
Kornel
this was already there - I fixed the location of the celeste.model so
that it is not mixed with the GUI elements. Are you sure you updated the
whole tree before building?
Hmm yes, I am always updating before compile.
(I was sending this e-mail _before_ your change, but it was delayed for 20
hours)
http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/trunk/src/hugin_config.
h.in.cmake?r1=4097r2=4096pathrev=4097
I still have a difference in my local tree. Celeste has not found
celeste.model, so I corrected the installation-place too.
Yuv
--
Kornel Benko
kornel.be...@berlin.de
Index: src/celeste/CMakeLists.txt
===
--- src/celeste/CMakeLists.txt (revision 4101)
+++ src/celeste/CMakeLists.txt (working copy)
@@ -94,6 +94,6 @@
)
INSTALL(TARGETS celeste_standalone DESTINATION ${BINDIR})
-INSTALL(FILES ${CELESTE_MODEL} DESTINATION ${HUGINDATADIR})
+INSTALL(FILES ${CELESTE_MODEL} DESTINATION ${INSTALL_DATA_DIR})
add_subdirectory(training)
signature.asc
Description: This is a digitally signed message part.
[hugin-ptx] Re: Celeste not compilable
Yuval Levy wrote: Note to myself for next time: xargs rm install_manifest.txt before testing! even better: added uninstall target to CMake build (SVN4104). make uninstall will remove Hugin cleanly. Now I have no more excuses for not properly testing :) Yuv --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Celeste not compilable
Am Sonntag 26 Juli 2009 schrieb Yuval Levy: Yuval Levy wrote: Note to myself for next time: xargs rm install_manifest.txt before testing! even better: added uninstall target to CMake build (SVN4104). make uninstall will remove Hugin cleanly. Now I have no more excuses for not properly testing :) Yuv There is one more: Installing as package. This will take care of such things. But it has a drawback nowadays. Because of the version .00 ubuntu tries later to upgrade hugin to version 0.7. I followed the discussion about the new schema and didn't care, sorry. But now it strikes. Kornel -- Kornel Benko kornel.be...@berlin.de signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Re: Celeste not compilable
Kornel Benko wrote: There is one more: Installing as package. This will take care of such things. Packages are for distribution. Trunk is for development. I see no reason to make packages when building for a local machine, and even less reason to make packages from trunk. Want a package? branch, update the version number in the root CMakeLists.txt to whatever suits the packaging system and release an alpha, beta, or release candidate. Yuv --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Celeste not compilable
Kornel Benko wrote: Hi, I got this error compiling trunk: ... /usr/src/hugin/hugin/src/hugin1/hugin/huginApp.cpp: In member function ‘virtual bool huginApp::OnInit()’: /usr/src/hugin/hugin/src/hugin1/hugin/huginApp.cpp:164: error: ‘LINSTALL_DATA_DIR’ was not declared in this scope ... With attached patch it compiles again. Kornel this was already there - I fixed the location of the celeste.model so that it is not mixed with the GUI elements. Are you sure you updated the whole tree before building? http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/trunk/src/hugin_config.h.in.cmake?r1=4097r2=4096pathrev=4097 Yuv --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
