> On Apr 11, 2019, at 1:28 PM, Pascal <p....@orange.fr> wrote:
>
>
>> Le 10 avr. 2019 à 01:27, John Ralls <jra...@ceridwen.us> a écrit :
>>
>>> On Apr 6, 2019, at 1:24 PM, Pascal <p....@orange.fr> wrote:
>>> John,
>>>
>>> Those folders were created by the script, I changed gtk-osx-setup.sh (also
>>> in pull request):
>>> - eval "mkdir -p $_varname"
>>> + mkdir -p "${!_varname}"
>>>
>>> I run again the script and I was surprised to see additional installations.
>>> It depends if you add python 3 path in PATH.
>>> With only one run, the installation seems incomplete.
>>>
>>> See attached log file.
>>
>> Pascal,
>>
>> The log file looks right. Did you have trouble running jhbuild?
>>
>> I reworked a bunch of things in gtk-osx-setup.sh including a complete
>> rethink on envvar()'s variable quoting. The way I'd written it before didn't
>> work if there were spaces in the path, the new way does.
>>
>> I'm still having trouble with the pyenv automatic installation getting
>> recognized, but you've avoided that by having a Python3 installation already
>> from which it just makes a virtenv and moves on.
>
> Hello John,
>
> I haven't run yet jhbuild cause of some additional fixes:
> - Fix some $HOME references.
> - Fix test for .jhbuildrc file.
> See last 2 commits of
> https://github.com/Blady-Com/gtk-osx-build/commits/proposal_01.
>
> Having also some questions:
> - is $HOME mandatory for PIP_CONFIG_DIR (line 48)?
> - is $HOME mandatory for .jhbuildrc and .jhbuildrc-custom (lines 214, 219)?
>
> For some reasons, I want to install all gtkosx stuff including building tools
> on an external volume (not on my home volume). But .local and jhbuild folders
> are yet created in my $HOME.
> How to do it properly?
You can put PIP_CONFIG_DIR anywhere you want, just set it before running
gtk-osx-setup.sh, e.g.
PIP_CONFIG_DIR=/Volumes/Development/pip_config gtk-osx-setup.sh
That works for all of the environment variables that are set with envvar().
$HOME/.jhbuildrc is hardcoded into jhbuild and jhbuildrc-custom is hardcoded
into jhbuildrc, so you're sort-of stuck with them. You can of course put the
real files somewhere else and symlink them to $HOME. I have a primary gtk-osx
checkout and symlink jhbuildrc-gtk-osx from there to $HOME/.jhbuildrc and I
keep my .jhbuildrc-custom under version control on a local server to make it
easy to share among my various macs and VMs.
We *could* configure .jhbuildrc-custom's location with yet another environment
variable, though I'm not too sure that it would be very useful to do so.
Regards,
John Ralls
_______________________________________________
gtk-osx-users-list mailing list
gtk-osx-users-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-osx-users-list
