- Jun 6, 2020
- 11,559
- 4,422
In support of using the Integrated B4JPackager11 I have the following code:
B4X:
This has been working well, however yesterday I found that the resultant installer did not include that "troublesome" jssc.dll even though jssc.dll had been copied to temp\build\bin\ and I now suspect it is due to the delay on my machine of completing the copying of that file to temp\build\bin\ before the InstallerScript.iss script is run.
To confirm my suspicion I commented out:
B4X:
and ran InstallerScript.iss manually. This resulted in an installer which now contained jssc.dll.
So:
B4X:
کد:
محتوای بلوک کدها در دسترس شما نیست. برای مشاهده بلوک کدها، وارد انجمن شوید یاثبت نام کنید
This has been working well, however yesterday I found that the resultant installer did not include that "troublesome" jssc.dll even though jssc.dll had been copied to temp\build\bin\ and I now suspect it is due to the delay on my machine of completing the copying of that file to temp\build\bin\ before the InstallerScript.iss script is run.
To confirm my suspicion I commented out:
B4X:
' #CustomBuildAction: After Packager, C:\Program Files (x86)\Inno Setup 6\Compil32.exe, /cc ../InstallerScript.issand ran InstallerScript.iss manually. This resulted in an installer which now contained jssc.dll.
So:
- Does each subsequent CustomBuildAction wait for completion of the...
برای دیدن لینک ها باید ثبت نام کنید
برای دیدن لینک ها باید ثبت نام کنید