First off, while we don't intend for there to be anything secret about
building emc2 packages on Ubuntu 10.04 or 8.04, I still recommend that
users who build their own use run-in-place. This is the easiest way to
build your own version, the fastest to rebuild for small modifications,
and it will never conflict with a packaged version.
If there's some annoyance of run-in-place, perhaps we should talk about
that. For instance, some users have been frustrated that with
run-in-place there are no Applications entries by default. But in
current versions you can create menu entries for a RIP EMC2 with
"make install-menus". I think this is undocumented so far, which is
unfortunate, but the capability is there.
Anyway, If you are on a version of Ubuntu that we build packages for,
then you can build a .deb package of emc2 and then install it. Starting
in the top director of a pristine copy of the emc2 source tree (not one
where you've already built "run-in-place"), here are the steps to build
a package:
debian/update-dch-from-git
# update debian/changelog from git history
# (so it's best if you've "git commit"ed your
# own local changes so they're listed in
# changelog)
# and then
debian/configure -r # generate debian files for running kernel
# or
debian/configure sim # generate debian files for no-realtime
# finally
dpkg-buildpackage -B -ub
If the dpkg-buildpackage step prompts you to install
packages, then do so and run that step again. (dpkg-buildpackage
builds the pdf documentation, which pulls in a lot of extra packages
that are not necessary for an RIP build that doesn't build documentation.
There are no plans to change this or make it optional. On Ubuntu 10.04,
remember to install these packages with "--no-install-recommends" to
reduce the number of extra packages to a minimum.)
This will generate debian packages (*.deb) in the parent directory.
You can install this package using 'dpkg -i' the emc2 and emc2-dev deb
files. (the exact filenames depend on the emc2 version number,
architecture, and sim vs rtai)
If you leave the linuxcnc.org package repositories in your apt
configuration, then some future release of emc2 may still appear as an
updated version. For example, if you built the v2.4_branch today and
installed that deb, then the next bugfix version will be a newer version
and will replace your self-built version if you agree to it in the
update manager. apt has ways to manage preferred versions of software;
search the web to find them.
These instructions may work for other debian-based distros, assuming
that their naming conventions for the kernel and rtai packages are
similar enough to the ones we've adopted on ubuntu.
If you use a different distro, then learn how to make an emc2 package
in cooperation with your OS's packaging system. For instance, a user
has contributed a way to build emc2 for Arch Linux:
http://neo-technical.wikispaces.com/emc2-arch
I recommend to *NEVER* do a bare 'make install' with emc2. There is NO
'make uninstall' rule and we have no plans to add one--I firmly believe
that installing/uninstalling software is a job for the OS's package
manager, and that "make uninstall" is a fundamentally broken idea (and
at any rate, it's not needed if the only use of 'make install' is to
serve the OS package builder).
If you do 'make install' on an Ubuntu system, the installation is
different enough from the one you get with a package that any deb you
install (or any deb you had already installed) will be subtly or
not-so-subtly broken by the files installed by "make install". Don't do
this; use a package management system instead. (on the other hand, when
building the package, there will be a 'make install DESTDIR=...' step
that puts all the files in a location that the package manager will use
to assemble the binary package)
Jeff
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
