VMware Communities: Message List - bug with -OutDir switch and tlink.exe ?

Re: bug with -OutDir switch and tlink.exe ?

Tejashri — Mon, 22 Jun 2009 03:56:16 GMT

Hi arodulr,

Have you tried with "OutDir" parameter in Package.ini? The OutDir parameter specifies the directory that stores the build.bat output. By default it is "bin" directory. You can set it with any name.

e.g. BuildOptions

OutDir=Test1

After setting the parameter in Package.ini, rebuild the package. Virtualized exes are copied in new Output directory specified against "OutDir" parameter.

Thanks & Regards,

Tejashri Khopkar

Re: bug with -OutDir switch and tlink.exe ?

arodulr — Sun, 21 Jun 2009 19:18:32 GMT

Hi Thinstall2,

Thanks for you suggestion: I didn't try to only modify package.ini with a custom bin path, I'll try that ASAP. However building the .tfd files with vftool.exe and vregtool.exe into a custom output dir is not a problem as I wrote. So maybe the temp dir for tlink.exe must be bin and the output dir can be anything else.
But having to modify package.ini (or having multiple package.ini) in order to build to different directory is not a very cool feature. I think the command line options should allow to do that, and package.ini should reference variables set at the command line ($BIN or something).
Or maybe I didn't understand how things work.

Any idea ?

Re: bug with -OutDir switch and tlink.exe ?

Thinstall2 — Sun, 21 Jun 2009 17:12:12 GMT

Have u ever let ThinApp complete its built? When I supply a custom "bin"-path in package.ini it The temporary buildfiles is still placed in bin, but when theyre completed vftool moves them to the output-path youve specified. Haven't messed with the bat-files yet though.

bug with -OutDir switch and tlink.exe ?

arodulr — Fri, 19 Jun 2009 11:26:00 GMT

Hi,

I was experimenting with a custom build.bat to generate the package into %PROJECT_DIR%\bin2 instead of %PROJECT_DIR%\bin as set up in the default build.bat.
vregtool and vftool don't seem to have problem with that:

"%THINSTALL_BIN%\vregtool" "%PROJECT_DIR%\bin2\Package.ro.tvr" ImportDir "%PROJECT_DIR%"
IF ERRORLEVEL 1 GOTO failed

"%THINSTALL_BIN%\vftool" "%PROJECT_DIR%\bin2\Package.ro.tvr" ImportDir "%PROJECT_DIR%"
IF ERRORLEVEL 1 GOTO failed

But for some reason, tlink is always searching into the default bin output dir even if I use the -OutDir switch:

"%THINSTALL_BIN%\tlink" "%PROJECT_DIR%\Package.ini" -OutDir "%PROJECT_DIR%\bin2"
IF ERRORLEVEL 1 GOTO failed

I get:

Could not initialize registry file: bin\Package.ro.tvr
Could not obtain lock file bin\Package.ro.tvr.lck
Press any key to continue...
*** Build failed ***

Moreover, there are path to the build directory inside package.ini, but even if I modify them, tlink is still looking for a bin output dir:

OutDir=bin2
...
[http://IrfanView 4.23.exe|http://IrfanView 4.23.exe]
ReadOnlyData=bin2\Package.ro.tvr
Source=%ProgramFilesDir%\IrfanView\i_view32.exe
FileTypes=.acr.aif.ani.asf.au.avi.b3d.bmp.cam.clp.cr2.crw.cur.dcm.dcx.dds.dib.djvu.ecw.emf.eps.exr.flv.fpx.fsh.g3.gif.gsm.hdp.icl.ico.iff.img.iw44.j2k.jng.jp2.jpc.jpe.jpeg.jpg.jpm.kdc.lbm.ldf.lwf.med.mid.mng.mov.mp3.mpe.mpeg.mpg.ngg.nlm.nol.ogg.pbm.pcd.pcx.pgm.png.ppm.psd.psp.ra.ras.raw.rgb.rle.rmi.sff.sfw.sgi.sid.snd.sun.swf.tga.tif.tiff.ttf.wav.wbmp.wdp.wma.wmf.wmv.xbm.xpm
Shortcuts=%Programs%\IrfanView

So how can I build a same project tree into different output directories without making a full copy of the project tree ?
The purpose is to build one package with different licensing enforcement scripts.

Thanks

Alban

PS: I found this same behaviour from Thinstall 3.3 to ThinApp 4.0.3 RC