I've committed an "improved" version of jallib script. My mistake was to pass through the shell, using python call to os.system. Now it passes args directly to the executable script, by-passing the shell.
This should remove issues about cmd line length limited by shell (it may remain limit about how much can be directly passed to the executable, I just dunno). Can you give another try ? I'm looking for a nice way to build a win32 executable by the mean time... Seb Le Sunday 05 October 2008 11:16:13 Joep Suijs, vous avez écrit : > Hi, > > For your infomation, I checked it on my system (XP with cygwin): > > This is a simple command line from (cygwin) make: > "/cygdrive/c/MyRobot/jal/jalV24/jalv2.exe" flipflop.jal -long-start > -s "C:\MyRobot\jal\jalV2\lib" > > And this is in the ams file: > c:\MyRobot\jal\jalV24\jalv2.exe flipflop.jal -long-start -s > C:\MyRobot\jal\jalV2\lib > > And for jallib, my commandline is: > "/cygdrive/c/MyRobot/jal/jalv24/jalv2.exe" jallib.jal -long-start -s > `/usr/bin/find /cygdrive/c/jallib/ -type d | perl inc.pl` > > (now I recall again: I need the cygwin shell to execute the `` part > before calling the compiler) > > And the result is an 17164 bytes command line. It looks to work okay, > though. But if I paste this to a dos box, it is clipped at 8191 bytes and > does not work. Running it from a batch file gives the message 'input line > too long'. > I suspect that the 17164 bytes are never handled like a command line, > but passed like an argv array. > > Joep > > -- Sébastien LELONG http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
