Idiot's guide to compiling...?

[MWheatley]

It's years since I compiled anything with QB64 -- I normally just run or edit in the IDE.  But a forthcoming move to a 64-bit machine means that it will be easier to have programs pre-compiled, as they rarely change.  Some of them were last updated several years ago.

So I could use a reminder on what to do.

Under "run" in the IDE the option "Output EXE to source folder" doesn't seem to do anything.

"Make EXE only" simply produces a gcc error that takes me around in a loop, needing Task Manager to execute a forced halt.

I'm running on a 32-bit machine, with QB64 1.3.

Malcolm

[Pete]

I'm on a 64-bit machine, and I don't experience those problems. I wonder if this is some incompatibility you stumbled upon, since you are running on a 32-bit machine? Hopefully, others will chime in to share their experiences.

Pete

[bplus]

Hi Malcolm,

Is your version 32 bit or 64 bit? QB64.org homepage offers 1.3 for both.

[MWheatley]

I see from my download history that I downloaded both versions.  I often do this, as I also have 64-bit machines.

The present 32-bit machine is my main machine, though.

Is there any way to tell from the IDE, or anywhere else, which version I installed?

I can't think of a reason why I would install the 64-bit version on a 32-bit machine, but -- hey -- mistakes happen.

Malcolm

[bplus]

My 64 bit version has numbers, Git 96937f0, in IDE Menu Help > About

If worse comes to worse, just download the sure 32 bit version.

[MWheatley]

Mine has the same Git number.  The title bar, though, proclaims it as "QB64 x32", I've just noticed.

That presumably means 32-bit?

Screenshot attached.

Malcolm

[FellippeHeitor]

That presumably means 32-bit?

Yes.

[MWheatley]

I've done a bit more experimentation.

With QB64 v1.2, everything works as it always did -- I can start and run programs (from the Run menu), and make EXE files to run separately on a standalone basis.

With QB64 v1.3, I can do neither.  I get the message in the attached image, which takes me into a loop from which Task Manager is the only way out.

Malcolm

[Raven_Singularity]

Check your anti-virus/anti-malware apps to see if they are blocking the compile.  Real viruses often recompile themselves to avoid detection, so the virus apps often look for apps recompiling.  You can usually add an exception for individual exe file, such as QB64's exe.

[SMcNeill]

Check your anti-virus/anti-malware apps to see if they are blocking the compile.  Real viruses often recompile themselves to avoid detection, so the virus apps often look for apps recompiling.  You can usually add an exception for individual exe file, such as QB64's exe.

I would guess this is the problem as well.  You may have whitelisted version 1.2 in the past, or the folder it’s in, and your antivirus ignores it and lets it work; while version 1.3 is now being blocked/quarantined again.

[MWheatley]

I would guess this is the problem as well.  You may have whitelisted version 1.2 in the past, or the folder it’s in, and your antivirus ignores it and lets it work; while version 1.3 is now being blocked/quarantined again.

Version 1.2 wasn't whitelisted (and I didn't remember whitelisting it, either).  But version 1.3 is whitelisted now.

Later today I will test it.

Malcolm

[FellippeHeitor]

Version 1.2 wasn't whitelisted (and I didn't remember whitelisting it, either).  But version 1.3 is whitelisted now.

Later today I will test it.

Malcolm

It's a good idea to whitelist the whole QB64 folder instead of only qb64.exe.

[MWheatley]

It's a good idea to whitelist the whole QB64 folder instead of only qb64.exe.

Done that; didn't make any difference.  Gimme a day or so -- I can try on a 64-bit machine.

Malcolm