[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Win32] tmp issue & NSI (was: Re: [Demexp-dev] Succesful compilation of

From: David MENTRE
Subject: [Win32] tmp issue & NSI (was: Re: [Demexp-dev] Succesful compilation of DemExp under Win32/Cygwin)
Date: Fri, 04 Mar 2005 23:48:42 +0100
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

Hello Christophe,

GISQUET Christophe <address@hidden> writes:

> I confirmed this is the cause of the error. Plus it should allow the
> application to run (the error is really fatal). So, unless I mixed
> things, it seems that changing "/tmp/" to, for instance, "C:\\" fixes
> the executiong. For some reason, it must look for a Cygwin install
> folder, as renaming mine to C:\Dev\_cygwin would cause the same problem
> as for all win32 users that tried the installer so far.

Ok, I think I have properly fixed the bug using OCaml platform indepent
Filename.temp_file (in demexp--cduce--0.3 branch):

val temp_file : string -> string -> string

  temp_file prefix suffix returns the name of a fresh temporary file in
  the temporary directory. The base name of the temporary file is formed
  by concatenating prefix, then a suitably chosen integer number, then
  suffix. The temporary file is created empty, with permissions 0o600
  (readable and writable only by the file owner). The file is guaranteed
  to be different from any other file that existed when temp_file was
  called. Under Unix, the temporary directory is /tmp by default; if
  set, the value of the environment variable TMPDIR is used
  instead. Under Windows, the name of the temporary directory is the
  value of the environment variable TEMP, or C:\temp by default.

Moreover, I have modified the Makefile so that client building no longer
needs CDuce. That should allow you the build the client of the
demexp--cduce--0.3 branch without installing Cduce (and all its
dependencies). And there is a new make target 'client' that builds both
native code and bytecode versions of the client.

If you have time to build a new version, let me know if it works under

Regarding NSI config files, I would like to integrate them in current
source tree once they're stabilized. If you have suggestions on how to
do that properly (and even a patch!), I would be glad to hear them.

Still for NSI config files, the "official" name of the demexp program is
'demexp' (and not DemExp). Simplicity is supposed to be a virtue. ;)

Once again, many thanks for all your work.
pub  1024D/A3AD7A2A 2004-10-03 David MENTRE <address@hidden>
 5996 CC46 4612 9CA4 3562  D7AC 6C67 9E96 A3AD 7A2A

reply via email to

[Prev in Thread] Current Thread [Next in Thread]