|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > New option to specific the output directory from slmake command line
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > New option to specific the output directory from slmake command line
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| New option to specific the output directory from slmake command line - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Min Member
|
I believe this option will be of great help to the effort of integrating slmake as one of steps of the post-build event of a compiler, in a team development environment. Basically the option will be something like (say the option name is -o): slmake.exe build <project>.slp -o <dirname> note here I am talking about the directory name, not the output file name. with this option, following script for post-build event in Visual C++ will work properly: "c:\Program Files (x86)\Sisulizer 2008\slmake.exe" scan build $(ProjectName)D.slp -o $(ProjectDir)\$(ConfigurationName) At the moment, without this sort of option, it is very inconvenient of integrating slmake due to the "hard-coded" output directory name in the .slp file, in a team development environment, as we would like make this post-build step work for different workstations, which likely have different directory settings. What do you think? Cheers Min
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Min, We are discussing this internally. In the moment we are pretty busy so we can not guarantee some fast solution. Workaround for now: While Sisulizer's project file is actually a XML file you might want to make a copy of it, patch the output path in the copy with some custom application and use in your build process before the call of SLMAKE. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
ccy Member
|
I am waiting for this option too.
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:05 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > New option to specific the output directory from slmake command line | |
Sisulizer software localization tool - Three simple steps to localize
