[Geany-Devel] OSX plugin development

Sun Oct 1 09:35:08 UTC 2017

Hi Steve,

yeah, I meant a different login.

Oh, you use MacPorts too. I had some problems with MacPorts and jhuild in
the past so that definitely could be it as well.

Jiri

On Sun, Oct 1, 2017 at 6:56 AM, Steven Blatnick <steve8track at yahoo.com>
wrote:

> Thanks again for the quick reply.
>
> When you say to use a separate account, do you mean a different login to
> osx? I'm not sure I can do that since this is a laptop I was issued from
> work that I wish to use geany plugins on. I think my best bet is to
> uninstall any homebrew (and macport?) gtk libraries and try again.
>
> Sorry I made you repeat your initial advice. I should have mentioned I
> didn't think I could try another account. If removing homebrew and deleting
> the gtk directory don't fix it, I suppose using jhbuild python is my next
> best option from your original email.
>
> Thanks,
>
> Steve
>
>
> -------- Original Message --------
> From:Jiří Techet
> Sent:Sat, 30 Sep 2017 13:15:16 -0600
> To:Geany development list
> Subject:Re: [Geany-Devel] OSX plugin development
>
> Hi Steve,
>
> I found this issue
>
> https://gitlab.kitware.com/cmake/cmake/issues/17101
>
> not sure if it's related.
>
> In your case I suspect either some clash with Homebrew (in this case I
> recommend building in a separate account) or that you built part of the
> dependencies on previous macOS system and then upgraded to High Sierra
> where symbols in system libraries may differ. In this case I'd suggest
> deleting the whole gtk directory and starting over to make sure everything
> is built on the new system.
>
> Jiri
>
>
>
> On Sat, Sep 30, 2017 at 1:09 AM, <steve8track at yahoo.com> wrote:
>
>> Ok, so I got through the dependencies (meta-gtk-osx-core), and ran:
>>
>>
>>
>> export LC_ALL=en_US.UTF-8
>>
>> export LANG=en_US.UTF-8
>>
>> jhbuild -m geany.modules build geany-bundle
>>
>> …
>>
>> *** Building libgit2 *** [14/26]
>>
>> make -j 9
>>
>> [  0%] Linking C shared library libgit2.dylib
>>
>> [ 79%] Built target libgit2_clar
>>
>> dyld: lazy symbol binding failed: Symbol not found: _utimensat
>>
>>   Referenced from: /Users/sblatnick/gtk/inst/bin/cmake
>>
>>   Expected in: /usr/lib/libSystem.B.dylib
>>
>>
>>
>> dyld: Symbol not found: _utimensat
>>
>>   Referenced from: /Users/sblatnick/gtk/inst/bin/cmake
>>
>>   Expected in: /usr/lib/libSystem.B.dylib
>>
>>
>>
>> make[2]: *** [libgit2.dylib] Abort trap: 6
>>
>> make[2]: *** Deleting file `libgit2.dylib'
>>
>> make[1]: *** [CMakeFiles/git2.dir/all] Error 2
>>
>> make: *** [all] Error 2
>>
>> *** Error during phase build of libgit2: ########## Error running make -j
>> 9  *** [14/26]
>>
>>
>>
>>   [1] Rerun phase build
>>
>>   [2] Ignore error and continue to install
>>
>>   [3] Give up on module
>>
>>   [4] Start shell
>>
>>   [5] Reload configuration
>>
>>   [6] Go to phase "wipe directory and start over"
>>
>>
>>
>> I’m not sure what is going wrong with building geany itself.
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Steve
>>
>>
>>
>> *From:* Devel [mailto:devel-bounces at lists.geany.org] *On Behalf Of *Jirí
>> Techet
>> *Sent:* Friday, September 22, 2017 3:02 AM
>> *To:* Geany development list <devel at lists.geany.org>
>> *Subject:* Re: [Geany-Devel] OSX plugin development
>>
>>
>>
>> Hi Steve,
>>
>>
>>
>> I slightly remember I got an error like this one in the past but I don't
>> remember what exactly the problem was. Anyway, it's not good to mix
>> dependencies from homebrew and jhbuild. If you have some environment
>> variables set up to link against homebrew libraries, this is what could
>> cause problems. I created a separate account on my machine from which I do
>> the Geany build to be sure nothing like that is set up.
>>
>>
>>
>> If you keep getting the error, you might also consider building python as
>> part of the build process which is then used instead of the system python
>> for the rest of the build. This means running
>>
>>
>>
>> jhbuild bootstrap
>>
>> jhbuild python
>>
>> jhbuild build meta-gtk-osx-bootstrap
>>
>> jhbuild build meta-gtk-osx-core
>>
>>
>>
>> When doing a change like that, it's best to remove the gtk directory
>> because it changes dependencies and basically everything has to be rebuilt.
>>
>>
>>
>> Apart from that everything else should work as described here:
>>
>>
>>
>> https://github.com/geany/geany-osx
>>
>>
>>
>> When al the dependencies are built, you should be able to use the same
>> stuff you use under linux for building your plugin. But be sure to run the
>> build within a jhbuild shell - you need to run
>>
>>
>>
>> jhbuild shell
>>
>>
>>
>> which sets up the environment variables to use the dependencies built by
>> jhbuild after you should be able to build your plugin in a normal way.
>>
>>
>>
>> Let me know if you run into more problems.
>>
>>
>>
>> Cheers,
>>
>>
>>
>> Jiri
>>
>>
>>
>> On Fri, Sep 22, 2017 at 12:00 AM, <steve8track at yahoo.com> wrote:
>>
>> I’m trying to build plugins in OSX, and I’m a bit out of my element.
>>
>>
>>
>> (I’ve had problems with my yahoo email not getting through to this list,
>> but I haven’t had a chance to switch email accounts.  I hope this makes it.)
>>
>>
>>
>> I’m following the guide on https://github.com/geany/geany-osx
>>
>>
>>
>> I get stuck running in step 6:
>>
>> jhbuild build meta-gtk-osx-bootstrap
>> …
>>
>> checking for python module libxml2... ./configure: line 2422: 83400
>> Done                    echo "import $py_module"
>>
>>      83401 Abort trap: 6           | python - >&/dev/null
>>
>> not found
>>
>> configure: error: Python module libxml2 is needed to run this package
>>
>> *** Error during phase configure of itstool: ########## Error running
>> ../configure --prefix /Users/steve/gtk/inst    *** [7/12]
>>
>>
>>
>>   [1] Rerun phase configure
>>
>>   [2] Ignore error and continue to build
>>
>>   [3] Give up on module
>>
>>   [4] Start shell
>>
>>   [5] Reload configuration
>>
>>   [6] Go to phase "wipe directory and start over"
>>
>>   [7] Go to phase "clean"
>>
>>   [8] Go to phase "distclean"
>>
>>
>>
>> I’ve installed libxml2 via homebrew, and py-libxml2 and py27-libxml2 via
>> macports to no avail.
>>
>>
>>
>> I figured out how to build the .o file for one of my plugins:
>>
>>
>>
>> gcc -c quick-search.c -fPIC -std=c99 -DGTK -I
>> /Users/steve/projects/geany/geany/plugins/ -I
>> /Users/steve/projects/geany/geany/src/ -I /Users/steve/projects/geany/geany/tagmanager/src/
>> -I /Users/steve/projects/geany/geany/scintilla/include/ `pkg-config
>> --cflags glib-2.0` `pkg-config --cflags gtk+-2.0` -I
>> /Users/steve/projects/geany/geany/scintilla/
>>
>>
>>
>> But not the ...so file.
>>
>>
>>
>> Thanks for any help,
>>
>>
>>
>> Steve
>>
>>
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.geany.org
>> https://lists.geany.org/cgi-bin/mailman/listinfo/devel
>>
>>
>>
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.geany.org
>> https://lists.geany.org/cgi-bin/mailman/listinfo/devel
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geany.org/pipermail/devel/attachments/20171001/96ac2e33/attachment.html>