On February 6, 2015 at 4:54:10 PM, Nicky Perian (nickyper...@gmail.com) wrote:
The issue was in fact paths. Operating with in the Developer Command Prompt for VS2013 requires a path of: C:\cwgwin64\bin;C:\cygwin64\usr\bin Reason: coreutils which contains printf and a host of other bash commands resides in C:\cygwin64\bin. Flex and Bison are installed in C:\cygwin64\usr\bin. So from Developer Command Prompt for VS2013 you can reach printf and flex and bison. Now the kicker if you now open the Cygwin64 Terminal the aforementioned C:\cygwin64\bin and C:\Cygwin64\usr\bin are mangled by cygwin64's remake of the path into the form /cygdrive/c/... and writes usr/bin;usr/bin in the path which breaks the path in Cygwin64 Terminal. If you don't include C:\cygwin64\bin and C:\Cygwin64\usr\bin in the path then cygwin64 is smart enough to figure it out and printf works in the Cygwin64 Terminal but, now it is broken in the Developer Command Prompt for VS2013. I'm thinking a workaround for this is to begin each windows batch file with a path command the appends C:\cwgwin64\bin;C:\cygwin64\usr\bin but do not put those in the system path. Hi, It would simply things greatly to remove lscript from the viewer completely, thereby removing the dependency on flex/bison for building. lscript is unused other than a few const values. Several tpvs have dropped lscript from the build. (I’ve personally done that in two different tpv projects.) Is this something Linden Lab would be willing to consider? I’d be happy to do the work to remove it if it is. -- Cinder Roxley Sent with Airmail
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
