You don't need to run it from the visual studio command prompt, you can run
it from a normal prompt as long as you use the whole path for cl. Also,
the same thing happens when I compile D code use dmd.
: test.d |> dmd -c%f |> test.obj
: test.obj |> dmd %f |> test.exe
The first rule will work and the second one will build but tup will say it
failed to save dependencies. Both MSVC (cl) and dmd are 32 bit compilers
and both fail for the same reason. I haven't used MinGW(gcc) but I can
give it a try. But why won't these other compilers work. Can someone else
try using MSVC and tup and see if they get the same results.
On Thursday, February 5, 2015 at 12:49:49 AM UTC-7, Freddie Chopin wrote:
>
> On 02/05/2015 12:39 AM, Jonathan Marler wrote:
> > I didn't even involve visual studio, all I'm doing is calling the 32
> > bit MSVC compiler directly from the command line (See the github issue
> > to be able to reproduce).
>
> Your github issue says:
>
> > REM run from Visual Studio Commandprompt (to have the"cl" program in
> thepath)
>
> As a starter try to run gcc directly from cmd ("normal" cmd), without
> anything fancy. I've been using tup on Windows for over 2 years and
> believe me - it works as advertised (; The only Windows limitations that
> I know of are 64-bit tools (solved recently, probably some problems
> still left) and lack of variants.
>
> Regards,
> FCh
>
--
--
tup-users mailing list
email: [email protected]
unsubscribe: [email protected]
options: http://groups.google.com/group/tup-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"tup-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
