[MonoDevelop] attempting git source compile of monodevelop (master)

[Jonathan Ballard]

Reviewed it, and (the) static build for F# IDE with LLVM codepaths (in
disassembly) makes sense if ObjC is present. That is quite minimal and
effective enough for that language's intended audience.

Without ObjC, LLVM means an esoteric wrapper around C++ mangle for
Java/JavaScript compatibility. Locale may be static or non-static in such
case.

Cheers!


On Wed, Jan 2, 2013 at 10:44 AM, Jonathan Ballard <dzonatas at gmail.com>wrote:

>
> These steps are quite old and not-stable beyond static library builds:
>
> """
> libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> Running aclocal  ...
> Running autoheader...
> Running automake --foreign  ...
> Running autoconf ...
> Running ./configure --enable-maintainer-mode --enable-compile-warnings
> --prefix=/home/jsr/local ...
> """
>
> If we unwrap parts of gnome inclusions, VS project file compatibility, and
> GCC dissembly (except for LLVM codepaths), we could replace the entire
> build above with more recent versions of mono and code.
>
> Despite said "dependency hell" of *SourceView, the minimal build option is
> desirable. It challenged developers that rather use VI or Notepad++;
> because they want their ideas written down and typed out before it is lost
> to ANY build complexities .
>
>
> On Wed, Jan 2, 2013 at 6:33 AM, Jeremy Reeve <jezz at kamelio.co.uk> wrote:
>
>> On Wed, 2013-01-02 at 14:14 +0000, Ian Norton wrote:
>> > Quite possibly your pkg-config files from the system's mono have got
>> confused
>> > with those of your build. That and you will probably have a mixed up
>> GAC now
>> > containing things from fedora and your build.
>> >
>> > You'll perhaps need to setup a parallel mono or remove the FC 17 mono.
>> >
>> > You can do this following
>> > http://www.mono-project.com/Parallel_Mono_Environments
>> >
>> > Ian
>>
>> The FC 17 mono isn't on the system - I removed it to guard against this
>> exact problem.  I forgot to mention that I set PKG_CONFIG_PATH to the
>> parallel mono install location to ensure the correct .pc files are
>> picked up.  It could still be something along those lines but since
>> removing FC17 mono I did rebuild all sources specifying --prefix.
>>
>> Having read the parallel environment link, I realise that I am not
>> setting:  ACLOCAL_PATH  .  Surely LD_LIBRARY_PATH not being set would
>> cause an earlier failure upon execution of the locally built mono tools
>> rather than the failure to compile generated sources as I'm seeing.
>>
>> I guess I can go back and use the script as supplied on the page and
>> rebuild everything again but to me it looks like there might be an
>> inconsistency between my installed system gnome development library and
>> what the gnome-sharp project expects (specified as version x.x.x >= n ,
>> but the later version I have is incompatible?) ...
>>
>> Thanks for pointing out the parallel mono env link regardless.
>>
>> Jeremy
>>
>>
>> _______________________________________________
>> Monodevelop-list mailing list
>> Monodevelop-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/monodevelop-list
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/monodevelop-list/attachments/20130103/cc02e98a/attachment.html>