![]() |
|
ForumTue Dec 10 11:21:27 2019 UTC CONFIGURE: Your examplesoyim ![]() Tue Dec 10 10:15:28 2019 UTC CONFIGURE: Your examplesThierry ![]() Tue Dec 10 08:58:31 2019 UTC CONFIGURE: Your examplesoyim ![]() Tue Dec 10 08:13:32 2019 UTC CONFIGURE: Your examplesThierry ![]() Mon Dec 9 11:19:07 2019 UTC CONFIGURE: Your examplesoyim ![]() Mon Dec 9 08:28:10 2019 UTC CONFIGURE: Your examplesThierry ![]() Mon Dec 9 07:33:08 2019 UTC Off-Topic: General discussionsoyim ![]() Mon Dec 9 07:30:44 2019 UTC CONFIGURE: Your examplesoyim ![]() Mon Dec 9 07:00:54 2019 UTC General: Newsoyim ![]() Sun Dec 8 18:05:07 2019 UTC General: Newssaleem ![]() |
Sun Feb 18 13:59:59 2018 UTC How to build a packageContentsIntroductionWe have provided the required Know-how, the available base commands, the minimum syntax of instructions and a list of available packages for you to choose from.
Come and join the many participants of all ages and gender, from all over the world, and venture along this exciting road we call NuTyX.
We can promise you a rewarding experience as you build your very first NuTyX system, following our (NuTyX) rules Build your first packageWe will show you how to build and install a first package in a very straightforward way. This tutorial explains to you in a very simple way the construction of your first binary package. They are no prerequisites. This exercise can be done regardless of the state of your NuTyX. The chosen package is a little text editor which doesn't need any dependencies. ![]() Make the build recipesudo mkdir -p /usr/ports/perso/nano echo ' description="Text Editor" maintainer="Nano team" packager="François Perrin francois dot perrin at myworld dot com" url="http://www.nano-editor.org/" name=nano version=2.7.2 release=1 source=(${url}/dist/v${version:0:3}/$name-$version.tar.xz) build() { cd $name-$version ./configure --prefix=/usr \ --sysconfdir=/etc \ --enable-utf8 \ --enable-color \ --enable-multibuffer \ --enable-nanorc \ --docdir=/usr/share/doc/$name-$version make make DESTDIR=$PKG install rm $PKG/usr/share/info/dir }' > /usr/ports/perso/nano/Pkgfile Install the development packagesget cards.devel Compile the packagecd /usr/ports/perso/nano sudo pkgmk -d Install the packagesudo pkgadd nano1* The configuration filesThe /etc/cards.conf fileThis file is always present on a NuTyX installation. It's a bit like "the spine" of your NuTyX. The /etc/cards.conf file will reflect the way you use NuTyX. All the collections that you want to use in your NuTyX can be specified in two ways:
This file is also responsible for the list of packages you want to keep when you execute the command: cards base -rAnd finally, it specifies which location should be installed. You can find more information by reading the cards.conf manual man cards.conf The /etc/pkgmk.conf fileThis file is used when compiling news ports. It specifies all the variables used by the pkgmk command. Please take the time to read the main page of pkgmk.conf man pkgmk.conf Example of /etc/pkgmk.conf fileexport CFLAGS="-O2 -pipe" export CXXFLAGS="${CFLAGS}" case ${PKGMK_ARCH} in "x86_64"|"") export MAKEFLAGS="-j$(getconf _NPROCESSORS_ONLN)" ;; "i686") export CFLAGS="${CFLAGS} -m32" export CXXFLAGS="${CXXFLAGS} -m32" export LDFLAGS="${LDFLAGS} -m32" ;; *) echo "Unknown architecture selected! Exiting." exit 1 ;; esac # Those settings are typically set for packaging # without sub packages and only French locations # They are also the default ones # # PKGMK_GROUPS=() # PKGMK_LOCALES=(fr) # PKGMK_COMPRESS_PACKAGE="no" # PKGMK_CLEAN="yes" # PKGMK_IGNORE_FOOTPRINT="yes" # PKGMK_KEEP_SOURCES="no" # PKGMK_SOURCE_DIR="$PWD" # PKGMK_WORK_DIR="$PWD/work" # PKGMK_IGNORE_REPO="yes" # PKGMK_IGNORE_COLLECTION="yes" # PKGMK_IGNORE_RUNTIMEDEPS="yes" ConclusionWe are now ready to build our packages in a chroot. |