GNU C++ Compiler error

[Jack]

I would copy/move all your basic files to the QB64pe-4.0.0 folder and work from there

[eoredson]

After merging the directories the same compilation error displayed.

With the .txt file:

So, instead deleted \qb64pe-4.0.0 and extracted it again and did a re-build and seems to work now.

[SMcNeill]

You *can not* merge and extract versions of QB64 on top of each other.

You *can not* copy versions of QB64 on top of each other.

You *can not* replace old drives or folders by simply transferring files to overwrite older versions.

We have said this over and over and over and over and over and over and over and over and over, and YET, with every release, there's at least a handful of folks who post, "HELP!  THIS DOESN'T WORK!! I CAN'T MERGE FOLDERS!!"....

From now on, my response to all these posts is just going to be:  "GOOD!!  YOU DON'T NEED TO PROGRAM ANYWAY!!  GO TAKE UP KNITTING!!"

(Gee @Pete -- maybe I'm going to become the NEXT Clippy..  It seems that a lot of his style may be necessary for the forums simply because nothing else works to get the message across to people.   )

[eoredson]

btw:

I have tested v4.0.0 with a memusage monitor which has cpu specific and ram displays and it works.
Also tested 32,000 lines of Sick and 53,000 lines of Qbshell and it works..

However due to the fact I cannot merge the two folders I am forced to manually copy them one by one!?

Erik.

[eoredson]

You *can not* merge and extract versions of QB64 on top of each other.

You *can not* copy versions of QB64 on top of each other.

You *can not* replace old drives or folders by simply transferring files to overwrite older versions.

We have said this over and over and over and over and over and over and over and over and over, and YET, with every release, there's at least a handful of folks who post, "HELP!  THIS DOESN'T WORK!! I CAN'T MERGE FOLDERS!!"....

From now on, my response to all these posts is just going to be:  "GOOD!!  YOU DON'T NEED TO PROGRAM ANYWAY!!  GO TAKE UP KNITTING!!"

(Gee @Pete -- maybe I'm going to become the NEXT Clippy..  It seems that a lot of his style may be necessary for the forums simply because nothing else works to get the message across to people.   )

Well, I apologize when I thought one new release of QB64pe would go into the same folder.

So, now I have two folders of the same product!?

You must bear with me because I have never done a complete build before...

Erik.

knit knit

[Jack]

eoredson
you can keep your \QB64pe  folder but delete everything that's related to the QB64pe installation and then extract the binary distribution into \QB64pe

[Steffan-68]

Or simply like me (I'm just lazy) create a BAT file that removes the entire QB64pe. Afterwards you can simply put the new one there again
copy into it.

Code: (Select All)

del copying.txt

del makefile

del qb64pe.1

del qb64pe.exe

del readme.md

rd /s /q internal

rd /s /q licenses

rd /s /q source

rd /s /q settings

[Kernelpanic]

I have already posted it four or five times: download the file, unpack it in a folder (for example UNPACK), from there move the whole qb64 folder to where you want it, then right-click and drag the qb64-pe.exe file to the desktop, select "Link here", and you're done. Takes about 10 minutes including downloading.

The settings for the IDE are now applied after a query.

[Pete]

Oh for ****'s sake, just do a *** **** fresh install and move all your **** over to the new *** **** qb64 folder!!!

@SMcNeill Hurry, send an exorcists!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Pete

[SMcNeill]

Oh for ****'s sake, just do a *** **** fresh install and move all your **** over to the new *** **** qb64 folder!!!

@SMcNeill Hurry, send an exorcists!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Pete

Even better:

Keep all your BAS files and personal stuff in a separate folder *OUTSIDE* the QB64PE folders.  Click the "Save EXE with Source" option.  

When a new version of QB64PE comes out, delete the old installation off your drive. extract the new version to the same place as before.   PRESTO!  That's probably all you need to do.  

Gosh, wasn't that complicated?