On 7/11/09 21:56, JiHO wrote:
>>> Or should I have copied the line into one of the files?
>
>> In the previous posting in that thread I described that I put the shell
>> environment configuration [2] into a shell script which I source
>> whenever I need the build environment set up (e.g. to run configure):
>
> This is precisely what osx-build.sh (in packaging/macosx/) is there
> for. Would you care to comment on why you don't use it?
Sorry if I don't use these scripts whenever I update from SVN. I ran the
autogen.sh/configure script quite some time ago, but since then I didn't
make a fresh checkout nor build from a released src package. Therefore I
have used neither autogen.sh nor configure lately and didn't research an
issue I had encountered with my first build attempts when I tried to
follow the wiki page step by step (skipping the first 'For the
impatient' section and using the 'recommended' instructions).
<off-topic>
When updating from SVN or testing patches I usually don't need to run
osx-build.sh because locally I have linked inkscape-bin to
'src/inkscape' (as well as some of the resources inside the bundle to
the corresponding subdirectories in 'src/Build/share/inkscape').
Due to an unsolved bug in MacPorts 1.8.x I haven't been able to update
the MacPorts dependencies since its upgrade to 1.8 which entailed same
basic changes to all portfiles that make them incompatible with older
'port' builds. Because of this I currently do not 'need' to re-bundle
newer libraries or resource files for gtk+ and the rest.
Once this bug in MacPorts is fixed (hopefully 1.8.2) I will again build
the full app regularly and try to report back any issues I encounter.
</off-topic>
> If you find that it gets outdated, please report it (not necessarily a
> full blown bug report but an email will be enough to start with). Now
> if I follow correctly, you are suggesting that
>
> export ACLOCAL_FLAGS="-I $LIBPREFIX/share/aclocal"
> export PKG_CONFIG_PATH="$LIBPREFIX/lib/pkgconfig:$PKG_CONFIG_PATH"
>
> should be added to osx-build.sh right? Wolf, if you could test whether
> that solves the problem on your system, tht would be nice. If it does,
> I'll add to once the trunk is reopened.
Going again through my old logs from the first attempts to build
inkscape because I can't remember the details... roughly these are the
steps I took (as fair as I can reconstruct it now):
source ../config_build.sh ### set build environment
./autogen.sh ### failed, after setting $ACLOCAL_FLAGS succeeded
cd packaging/macosx
./osx-build.sh c ### failed (libpng), $PKG_CONFIG_PATH didn't help
cd ../..
./configure --enable-osxapp \
--prefix=/path/to/inkscape/packaging/macosx/../../Build/
### configure succeeded, likely that $PKG_CONFIG_PATH helped (not verified)
cd packaging/macosx
./osx-build.sh p -py /path/to/Python-packages
Looking at this now it seems that the mix (src/autogen.sh and
packaging/macosx/osx-build.sh) didn't work (my mistake) i.e. once I
started with ./autogen.sh I needed to follow with ./configure using the
correct configure flags copied from osx-build.sh. But honestly I am
afraid that drawing this conclusion without re-testing isn't correct
either ;-)
Yet it most likely means that the build scripts in 'packaging/macosx'
don't need to be updated.
@ Wolf - sorry, AFAICT now my tips are wrong and you better stick to
using the build scripts in 'packaging/macosx' only and don't run
autogen.sh/configure by itself.
@JiHO - I'll try next week to build a fresh checkout or 0.47pre4
strictly using your scripts (without updating the MacPorts tree first)
and report back if I encounter any errors.
~suv (who shouldn't have answered without re-checking the build logs!)
|
