[GEM-dev] getting latest Gem into Pd-extended

[Ricardo Fabbri]

I didn't realize there was an active Git repository for Gem.
Although it is liked to at the Gem page (bottom-right link),
the Pd getting soucres page only mentions the SVN.
http://puredata.info/docs/developer/GettingPdSource

Which caused me to write further documentation based on that info.

So I would like to know if developers should abandon SVN
so that I can update some docs at puredata.info. I am curious to hear
the answers to Hans' questions.

Best,
Ricardo Fabbri
Linux registered user #175401



On Thu, Oct 20, 2011 at 2:59 PM, Hans-Christoph Steiner <hans at at.or.at> wrote:
>
> On Oct 20, 2011, at 12:20 PM, Hans-Christoph Steiner wrote:
>
>>
>> On Oct 20, 2011, at 4:09 AM, IOhannes m zmoelnig wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> On 2011-10-18 21:47, Hans-Christoph Steiner wrote:
>>>>
>>>> Hey IOhannes,
>>>>
>>>> I would like to include the latest version of Gem in Pd-extended 0.43.
>>>> It currently needs a little work.  It builds on GNU/linux, but gives a
>>>> missing symbol (something like _sync_foo_bar).
>>>
>>> it builds on "GNU/linux" without the missing symbols as well, else i
>>> coulldn't use it myself :-)
>>> i assume that this is on some ubuntu flavour (which one), with a certain
>>> compiler version (which one) and some special C(XX)FLAGS.
>>>
>>> according to the internet, adding something like "-march=i486" to the
>>> C(XX)FLAGS should help.
>>
>> I think that one might be might fault.  I made it so it set CFLAGS for Gem
>> in externals/Makefile.  I removed that, but haven't tested it again yet.
>>
>>
>>>> It doesn't build on Mac
>>>> OS X 10.5.
>>>
>>> what does "latest Gem" mean here?
>>> the git version (which is indeed the 'latest') of Gem has the issue
>>> fixed.
>>> the 'svn' version (both trunk and branch/0.93) and the releases have it
>>> not fixed (yet).
>>>
>>> if you want/must stick to the current release (which is fair enough) or
>>> svn, a very simple workaround would be to add /sw/bin to the beginning
>>> of the PATH before calling Gem's autogen.sh
>>
>>
>> I am waiting on definitive answers on two questions, until then, I'm
>> sticking to the  current setup.
>>
>> - are you dropping support for the Gem SVN?
>>
>> - are you dropping support for building on Mac OS X 10.5 without Fink?
>
> Oops, one more question:
>
> - are you planning on making Mac OS X builds?
>
> .hc
>
>
>
> ----------------------------------------------------------------------------
>
> I have always wished for my computer to be as easy to use as my telephone;
> my wish has come true because I can no longer figure out how to use my
> telephone."  --Bjarne Stroustrup (creator of C++)
>
>
> _______________________________________________
> GEM-dev mailing list
> GEM-dev at iem.at
> http://lists.puredata.info/listinfo/gem-dev
>