en en en en en en en en en en en en en en en en en en en en en en en en en en en ru en en en en en en en en en en en en en en en en en en en en nl en ru en en en en en en en en de fr en en en en nl en en en en en en fr en en fr pt en en fr en en en en nl en en en en en en en en en en en en en en en en en en en de en en en fr en en en en en en en en en pt en en en en en en
By logging into your account, you agree to our Privacy Policy, personal data processing and storage practices as described therein.
Forgot password or user name?
Search in titles only Search in PowerBASIC for Windows only
You are not logged in. You can browse in the PowerBASIC Community, but you must click Login (top right) before you can post. If this is your first visit, check out the FAQ or Sign Up.
All Time Today Last Week Last Month
All Discussions only Photos only Videos only Links only Polls only Events only
19 Mar 2000, 12:58 AM
I like to have a sub-directory called Release containing the application-exe-file, and a sub-directory called Resource containing the resource-files. Therefore i initialte my programs with:
The problem is that when i press ctrl+E (Build and Execute) to compile my program, the program is not executed. The reason is that PB tries to execute "MyProg.exe" instead of "Release\MyProg.exe". Is there a way to solve this problem ?
[This message has been edited by Peter Stephensen (edited March 19, 2000).]
Join Date: Aug 1998
19 Mar 2000, 01:25 AM
not at this time. this is covered in the faq forum http://www.powerbasic.com/support/pb...hread.php?t=32
the workaround is to place a shortcut on the desktop to the target exe, then open the properties to the shortcut and assign a "shortcut key" such as ctrl + alt + 1
this way you can launch the exe after compiling simply by pressing the chosen shortcut key combination.
Join Date: Sep 1999
19 Mar 2000, 02:39 AM
I selected more friendship variant.
I prefer another variant (release' files in main directory, source and resource modules in subdirectories).
To avoid such problems with exe I wrote small fictive module.
To be more clear, I describe a technique on your sample.
ONE TIME somewhere you compile this module
(let's name it fict.bas)
#Compile Exe #Register None #Include "Win32Api.Inc" DefLng A-Z Function PbMain Local TmpAsciiz As Asciiz * %MAX_PATH lResult = GetModuleFileName(ByVal 0, TmpAsciiz, SizeOf(TmpAsciiz) - 1) If lResult = 0 Then Exit Function i = 0 Do j = Instr(i + 1, TmpAsciiz, "\") If j = 0 Then Exit Do Else i = j Loop CatalogExe$ = Left$(TmpAsciiz, i) If Right$(CatalogExe$, 1)   "\" Then CatalogExe$ = CatalogExe$ + "\" ExeName$ = Mid$(TmpAsciiz, i + 1) y = Shell(CatalogExe$ + "Release\" + ExeName$, 1): Sleep 0 End Function
When you want to debug a new program, you copy fict.exe to a directory with BAS and rename it to myprog.exe.
Now you can use Compile.Exe "Release\Myprog.Exe", because IDE will start the fictive module from the same directory as BAS.
Fictive module defines full path (for example, C:\Prog\MyProg.Exe") and in own turn start C:\Prog\Release\MyProg.Exe (prepared by IDE).
Copyright © 1998-2022 PowerBASIC Tools, LLC - All Rights Reserved.
Powered by vBulletin® Version 5.7.0
Copyright © 2022 vBulletin Solutions, Inc. All rights reserved.
All times are GMT-5. This page was generated at 01:49 AM.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, and to analyze site activity. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.