[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Mingw-cross-env-list] gprolog
From: |
Tony Theodore |
Subject: |
Re: [Mingw-cross-env-list] gprolog |
Date: |
Thu, 03 May 2012 03:50:00 +1000 |
On 24/06/2011, at 12:22 AM, Tony Theodore wrote:
> Hi Alois,
>
> On 14 June 2011 18:22, Alois Schlögl <address@hidden> wrote:
>> Attached are the mk-files for building gprolog. Two versions, v1.3.1
>> (stable) and v1.4.0 (development), are included because I do know which one
>> is prefered in mce.
>>
>> The built process is broken, the make process seems to require to run some
>> *.exe (and asks for wine).
>>
>> I hope someone else can help with the remaining issue(s).
>
> This looks like it will be quite tricky - it seems to be a two step
> bootstrap where it first builds a config tool then a compiler to
> produce the final output. It also does cpu detection, which isn't
> ideal for cross-compiling. On the surface it seems like you'd have to
> build the initial parts natively and then "trick" the build system
> into using those.
>
> It also looks like the final output is more like an executable than a
> library. Are you using this in another project or simply trying to
> cross-build it to use standalone?
Hi Alois,
Are you still looking at this? From what I can gather from the website, it's
actually an interpreter that can compile to native code for extra performance.
There are several 32 and 64-bit windows binaries available (now at v1.4), so
you are most likely better off using those.
If you do want to cross-compile it, I'd suggest asking on the gprolog list
first - it doesn't seem like the sort of thing it's designed to do.
Cheers,
Tony
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Mingw-cross-env-list] gprolog,
Tony Theodore <=