Hi Martin,
GODI is currently broken on Windows, and I would need to invest again a
few days to get at least the basics running again. This is a big problem
for me, because I've personally no direct advantage from this, and there
is also the question how you can keep such a very different port runn
Better Windows support would be very nice too. A friend recently had a
python app that he wanted to port to native code, and I offered to do
it for him in OCaml. The linux version was quick and easy to develop,
and we both believed that he could just install OCaml and the required
libraries on wind
-[ Wed, May 04, 2011 at 11:20:36AM +0200, Fabrice Le Fessant ]
> > Will you share the results of this survey?
>
> Yes, of course, but I don't know yet at which level of details, as going
> into details might require to anonymize the responses.
So, nothing interresting emerged from that survey
Le 10/12/2011 15:45, Xavier Leroy a écrit :
>> For example, have a look at PR/3746, a great example. It took almost
>> 4 years(!) to update the ARM port to softfp (and EABI). At the time
>> the issue was finally fixed, most ARM application boards were
>> already shipping with VFP, so the port is la
Mehdi Dogguy writes:
> On 12/12/2011 11:59 AM, Benedikt Meurer wrote:
>>
>> On Dec 12, 2011, at 11:21 , Xavier Leroy wrote:
>>
>>> - It complicates the lives of OCaml users, packagers, and
>>> 3rd-party library developers: what version should they use? what
>>> will be the basis for the packag
>
> On Dec 12, 2011, at 11:21 , Xavier Leroy wrote:
>
>> - It complicates the lives of OCaml users, packagers, and 3rd-party
>> library developers: what version should they use? what will be the
>> basis for the packagers's distribution-specific patches? what
>> happens if a library is compat
I tried i686-w64-mingw32-gcc version in august, on a 32 bits system,
starting from the patches attached to
http://caml.inria.fr/mantis/view.php?id=5179.
I tested all those packages without problem:
menhir, bitstring, ounit,ocamlcsv, frontc, xmllight, camomile,
batteries, zlib, camlzip, lablgtk2
On 12/12/2011 11:59 AM, Benedikt Meurer wrote:
>
> On Dec 12, 2011, at 11:21 , Xavier Leroy wrote:
>
>> - It complicates the lives of OCaml users, packagers, and
>> 3rd-party library developers: what version should they use? what
>> will be the basis for the packagers's distribution-specific
>>
Dear caml-list,
The mingw port of OCaml was not in a good shape, because of changes in
Cygwin:
- We used to rely on the normal Cygwin gcc compiler, using the
-mno-cygwin flag. This is no longer available for recent versions
of gcc shipped in Cygwin. There is still a gcc-3.exe, but it
On Dec 12, 2011, at 11:21 , Xavier Leroy wrote:
> - It complicates the lives of OCaml users, packagers, and 3rd-party
> library developers: what version should they use? what will be the
> basis for the packagers's distribution-specific patches? what
> happens if a library is compatible with
On 12/10/2011 04:58 PM, Benedikt Meurer wrote:
> Maybe we can get back to my original proposal and restart on the
> right foot this time?
All right. I have a number of concerns about your proposal, most of
which have already been mentioned by others. Whether you call it a
fork or not, the mere
11 matches
Mail list logo
