|
|||
|
Hello,
I've got a small problem that I hope you can help me with. I've got a WORKING SKP file that's used to wrap my SWF into an EXE... When this SKP is moved over to our automated build machine, I need to be able to run SWFKIT from the command line. The PROBLEM I'm seeing is that SWFKIT is forgetting where my Movies and DLLs are even though I've VERY CAREFULLY duplicated the EXACT paths to the files in the HOPE that it would work. Is there any way to manually specify movies and dll that should be referenced to get around this problem? Better yet, is there anyway to make the file references survive the move to a new machine? It seems that what I'm doing SHOULD produce success, but I'm sure not seeing it. ALSO, if I specify the -s flag, I'm getting an exception. Shouldn't that be working correctly? (I'm using 3.09) Thanks in Advance, Steve |
|
|||
|
Thank you for your reply.
This is GREAT NEWS!! Do you happen to have any idea when this release will take place? I don't mean to be a pest, but I've got a build team ready to FLOG me for bringing them tools that won't integrate to their build system. THANKS Steve |
|
|||
|
OK, now we have SWFKit Pro 3.1 and the command-line for SWFKit works fine. Thank You!
You mentioned that version 3.1 also allowed useage of UpdateMaker from the command-line. How do we use UpdateMaker from the command line? There appears to be NO documentation at all. |
|
|||
|
The UpdateMaker tool now supports to be called from command line
updatemaker.exe -b [-s] -o:[output directory] filename -b build the updatemaker project specified by "filename" -s build the updatemaker project silently -o: specify the output directory of update files filename the updatemaker project to build For example: updatemaker.exe -b -s -o:c:\updates myupdates.umf |
![]() |
Was this information helpful? Yes No
| Thread Tools | |
| Display Modes | |
|
|