VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
3 Replies Last post: Jun 21, 2009 8:56 PM by Tejashri  

bug with -OutDir switch and tlink.exe ? posted: Jun 19, 2009 4:26 AM

Click to view arodulr's profile Novice 25 posts since
Jul 5, 2008
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

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

1. Jun 21, 2009 10:12 AM in response to: arodulr
Click to view Thinstall2's profile Enthusiast 44 posts since
Jul 29, 2008
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.

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

3. Jun 21, 2009 8:56 PM in response to: arodulr
Click to view Tejashri's profile Enthusiast 36 posts since
Jan 8, 2009

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

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities