[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Texmacs-dev] problems with self compiled versions after upgrading p
Re: [Texmacs-dev] problems with self compiled versions after upgrading port on OSX
Wed, 2 Apr 2014 10:06:31 +0200
On 31 March 2014 21:50, Miguel de Benito Delgado
> did you compile using XCode? Or was it make MACOS_BUNDLE? The latter should
> produce a valid .app (though it might not work 100% of the time, haven't
> checked recently)
> There's also the possibility of using Massimiliano's tm-devel-mac stuff.
> After some (possibly heavy) tweaking, one ends up with a complete
> installation from source of all the libraries required for TeXmacs, ready to
> be used with the ./configure. I must confess that I gave up after many hours
> of (fruitless) said tweaking, but YMMV.
Similar here (though I didn't use tm-dev-mac). It took several hours
of tweaking (mainly because of new versions of Xcode and the new
non-gcc compiler, etc), and now I don't remember if the final version
was compiled on Xcode or by the make script.
> On 28 March 2014 15:47, Michael Lachmann <address@hidden> wrote:
>> I had a version of TeXmacs I compiled myself from the SVN archive on OSX.
>> After upgrading my "ports" version on my mac (port selfupdate; port
>> upgrade updated) TeXmacs wouldn't run anymore. The problem was that
>> could not be found. I restored those files from a Time Machine backup,
>> and all seems to work again.
>> I know I should have done something so the app does not depend on
>> those external libraries... but in any case, if someone has the same
>> problem, this is one solution...
>> Texmacs-dev mailing list
> Texmacs-dev mailing list
|[Prev in Thread]
||[Next in Thread]|
- Re: [Texmacs-dev] problems with self compiled versions after upgrading port on OSX,
Michael Lachmann <=