| 2016-01-06 12:22:55 |
Andreas Pokorny |
bug |
|
|
added bug |
| 2016-01-11 13:52:53 |
Andreas Pokorny |
description |
When building multiple parts from source that depend on each other in a snapcraft session it would be useful if snapcraft would setup the environment for each part in a way that autotools/pkg-config/cmake can find the build results from 'after:'-parts. |
When building multiple parts from source that depend on each other in a snapcraft session it would be useful if snapcraft would setup the environment for each part in a way that autotools/pkg-config/cmake can find the build results from 'after:'-parts.
Or instead of setting up search paths it might just build & install in a dedicated chroot environment and build each part in the same environment.. |
|
| 2016-01-11 14:12:45 |
Sergio Schvezov |
snapcraft: status |
New |
Incomplete |
|
| 2016-01-12 23:52:44 |
Andreas Pokorny |
description |
When building multiple parts from source that depend on each other in a snapcraft session it would be useful if snapcraft would setup the environment for each part in a way that autotools/pkg-config/cmake can find the build results from 'after:'-parts.
Or instead of setting up search paths it might just build & install in a dedicated chroot environment and build each part in the same environment.. |
When building multiple parts from source that depend on each other in a snapcraft session it would be useful if snapcraft would setup the environment for each part in a way that autotools/pkg-config/cmake can find the build results from 'after:'-parts.
Or instead of setting up search paths it might just build & install in a dedicated chroot environment and build each part in the same environment..
Assume this snapcraft.yaml:
name: nfs-server # the name of the snap
version: 0.1 # the version of the snap
# The vendor for the snap (replace 'Vendor <email@example.com>')
vendor: Andreas Pokorny <andreas.pokorny@gmail.com>
summary: Simple NFS Server
description: Simple NFS Server setup for home server use, with manual user and exports setup
icon: folder-remote-nfs.png
architectures: [armhf]
parts:
libtirpc:
plugin: autotools
source: git://github.com/APokorny/libtirpc.git
source-branch: use-snappy-env
stage-packages:
- libkrb5-dev
filesets:
tir-files:
- lib/libtirpc.so*
snap:
- $tir-files
rpcbind:
plugin: autotools
source: git://git.linux-nfs.org/projects/steved/rpcbind.git
stage-packages:
- libwrap0-dev
after:
- libtirpc
nfs-utils:
plugin: autotools
source: git://github.com/APokorny/nfs-utils.git
source-branch: use-snappy-env
stage-packages:
- libcomerr2
- libnfsidmap2
after:
- libtirpc
After building libtirpc when building rpcbind configure fails because it cannot find libtirpc. The configure script uses pkg-config here. I assume snapcraft would use PKG_CONFIG_PATH and PKG_CONFIG_SYSROOT_DIR.
... |
|
| 2016-01-13 02:04:56 |
Sergio Schvezov |
snapcraft: status |
Incomplete |
Triaged |
|
| 2016-01-13 02:04:59 |
Sergio Schvezov |
snapcraft: importance |
Undecided |
High |
|
| 2016-01-13 02:05:04 |
Sergio Schvezov |
snapcraft: milestone |
|
2.0 |
|
| 2016-01-13 02:05:17 |
Sergio Schvezov |
nominated for series |
|
snapcraft/1.x |
|
| 2016-01-13 02:05:17 |
Sergio Schvezov |
bug task added |
|
snapcraft/1.x |
|
| 2016-01-13 02:05:17 |
Sergio Schvezov |
nominated for series |
|
snapcraft/trunk |
|
| 2016-01-13 02:05:17 |
Sergio Schvezov |
bug task added |
|
snapcraft/trunk |
|
| 2016-01-13 11:36:18 |
Sergio Schvezov |
snapcraft/trunk: status |
Triaged |
In Progress |
|
| 2016-01-13 11:36:20 |
Sergio Schvezov |
snapcraft/trunk: assignee |
|
Sergio Schvezov (sergiusens) |
|
| 2016-01-15 13:13:27 |
Sergio Schvezov |
snapcraft/trunk: status |
In Progress |
Fix Committed |
|
| 2016-01-21 18:05:57 |
Kyle Fazzari |
snapcraft/trunk: status |
Fix Committed |
Fix Released |
|
