DAV's IDE will not run EXE

[EricE]

I upgraded QB64 to version 1.4 and then found that DAV's IDE will not run the generated EXE.
Going back to QB64 version 1.3 DAV's IDE will compile and run the executable.

I am using the 32-bit versions of QB64 on a Windows 10 64-bit computer.

What could have changed between QB64 versions 1.3 and 1.4 to keep the IDE from running the EXE?

DAV's IDE
http://www.qbasicnews.com/dav/projects.php#DAVSIDE

[Dav]

I'll check it out. Thanks for the report.

can you look at your davside settings file and see if it's pointing to the new compiler path?

- Dav

[bplus]

With QB64 updates you have to remember to reset the bullet of saving EXE in source folder under Run Menu of IDE, if that's how you do things with QB64.

[EricE]

Hi Dav,
Compiler version, v1.3 or v1.4, was verified by opening the Dav settings file and checking the compiler path.
Version being used was also displayed during compilation of the source.

[EricE]

Hi bplus,
The DavsIDE option, "Compile>Compiler Options...>Save EXE at the BAS location", is checked.

[bplus]

Oh that's right, Dav would have that on his own IDE for compiler :)

[Dav]

Hi EricE.  I downloaded a fresh QB64 GL v1.4 32bit, along with the IDE.   I'm not able to duplicate the problem yet that you're getting.  EXE's are running after compile for me (I'm using Win7-32bit).   Not sure what to suggest right now, but I'll keep testing and try to find out what the problem could be. 

I don't know if there are any compiling changes from v1.3 to v1.4.  Maybe someone else can chime in on that.  I'm heavily leaning towards the problem is coming from a bug in my long neglected IDE and not in a QB64 change.

- Dav

[EricE]

I will check on my Win7 system if the problem is seen.
If the issue is not seen on that computer, then it might be a Windows 10 issue with version 1.4.

[EricE]

Here is some more information for the Windows 10 computer.
Using DavIDE and QB64 v1.4 to compile my test program will result in a temporary exe being created by the name of "_$DavsIDE-TEMPFILE.exe".
This exe is the executable for my program.
It appears that on a Win10 computer DavIDE cannot rename the temporary exe if QB64 version 1.4 is being used.

[Dav]

Thank you, EricC.  That is very helpful to know the compiling is taking place.   Does the temp EXE run as expected?  My IDE should handle the temp EXE the same way regardless of QB64 version.  Strange that it's not. It may be a Win10 thing.  I think I have a Win10 laptop somewhere to test on.  I'll dig it up.

Question...does your path names or filenames have a space in them?

- Dav 

[SMcNeill]

Or is it a anti-virus or folder permission issue? 

[EricE]

I have DavsIDE working now, running the generated EXE after the QB64 compiler compiles the source code.

What I did was to uninstall the QB64 versions, both 1.3 and 1.4, by deleting the folders containing them, and then reinstalling the versions in these folders:

• C:\qb64_1.3_win_x86\qb64
• C:\qb64_1.4_win-x86\qb64

Then running only one instance of DavsIDE when testing (I had two instances of it open at the same time!) I was able to switch back and forth between the versions by setting the Compiler options.

Thank you Dav and everyone for your suggestions regarding this.

[EricE]

I have reproduced the problem, and found that it is due to having two instances of DavsIDE opened and with each set to use a different version of QB64 with different config settings.

DavsIDE's setting "Save EXE at the BAS location" was set to TRUE and the QB64's config.txt file setting SaveExeWithSource was set to TRUE for one version of QB64, and to FALSE for the other version.

DavsIDE would not rename and run the executable built with the QB64 version that had it's SaveExeWithSource value set to TRUE.

See post #14 below.

[EricE]

Problem came back, but cause was discovered.

See post #14 below.

[EricE]

I found the essential cause of the issue.
There is a conflict between QB64's configuration setting "SaveExeWithSource" and DavsIDE's compiler option setting "Save EXE at the BAS location".

If the DavsIDE is to be used and it's setting is set to TRUE, then the QB64's setting must be set to FALSE.