Hi Robert, On Thu, Dec 5, 2013 at 5:13 AM, Robert Pettersen <[email protected]> wrote:
> Hi Mike, > > Sorry for the late reply, beeing swamped with work here. We are currently > porting our old makefile system to tup, for an operating system and all its > applications. And unfortunately half our developers are on FreeBsd and half > on Windows 8, so have taken some time porting all the tools. Just finished > the auto-tools last night (generate tupfiles etc.). So we are switching > today :) > No worries - I have been pretty swamped as well. How did the switch go? > > >>> One caveat I haven't figured out yet is command chaining. (i.e. "cmd1 && >>> cmd2") Tup encapsulates command chanining on Windows in a cmd.exe wrapper. >>> But cmd.exe on 64bit Windows seems reluctant to injection, or would need >>> some special handling. I have noticed that the process version for cmd.exe >>> differs from the other 64bit applications, but according to documentation I >>> have read this should only pertain to an extra MSDOS header saying that >>> this application cannot run on ms-dos... >>> I solved this by having a python script handing command chaining with >>> Popen for now. >>> >>> >> I run my tests on a 64-bit Windows 7 VM, but even there it seems cmd.exe >> is a 32-bit program. Is this the case on your machine as well? Are you >> loading the 32-bit DLL for it? Maybe it has something to do with the WoW64 >> layer? >> > > We are running on Windows 8, and here cmd.exe is 64 bit. But the file > format is "pei-x86-64", not "pe-x86-64" as is the case for the 64bit > applications that work. I will investigate more when I get around. > Any luck with cmd.exe? I think it would be great if that would work with the 64-bit support as well, though maybe the python script could be provided as a work-around in the meantime. People have been asking for 64-bit support for a while now, so any progress we can make there would be very welcome. > > >> Let me know if you want to get this in the tree - I would need a license >> agreement (here: http://gittup.org/tup/icla.txt ) and of course a patch >> or github repo somewhere :) >> > > Yes, have to clean up the code a bit first, and fix the agreement and > github repo. > > Thanks Robert - please keep me posted! -Mike -- -- 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/groups/opt_out.
