Posts: 652
Threads: 96
Joined: Apr 2022
Reputation:
22
Help!!!
I've loused something up. 
Suddenly I can't run any of my .bas progs (they've all run previously). I get message Failed to compile C++ on all of them.
I think it's something to do with where the compiled file is placed, but I can't see how to change this. In the Run menu, the option to Output to Source Folder is selected.
Posts: 2,698
Threads: 327
Joined: Apr 2022
Reputation:
217
Can you click on the error message and post what it tells you here?
If all else fails, you can always grab a fresh download from the repo and extract it into a new folder, while getting rid of the old/corrupted version once you migrate your files over. 
Posts: 652
Threads: 96
Joined: Apr 2022
Reputation:
22
01-01-2023, 05:45 AM
(This post was last modified: 01-01-2023, 05:49 AM by PhilOfPerth.)
Thanks Steve.
I downloaded and re-installed in a new folder (re-named the old one as QB64PEOld to keep my files) , then copied all of my .bas files into it, but still get the same message: C++ Compilation failed (check .\internal\temp\compilelog.txt)
and that file had this:
<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family wiss; mso-font-pitch:variable; mso-font-signature:-469750017 -1073732485 9 0 511 0;} @font-face {font-family:Consolas; panose-1:2 11 6 9 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:modern; mso-font-pitch:fixed; mso-font-signature:-536869121 64767 1 0 415 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:0in; margin-right:0in; margin-bottom:10.0pt; margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} p.MsoPlainText, li.MsoPlainText, div.MsoPlainText {mso-style-priority:99; mso-style-link:"Plain Text Char"; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.5pt; font-family:Consolas; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} span.PlainTextChar {mso-style-name:"Plain Text Char"; mso-style-priority:99; mso-style-unhide:no; mso-style-locked:yes; mso-style-link:"Plain Text"; mso-ansi-font-size:10.5pt; mso-bidi-font-size:10.5pt; font-family:Consolas; mso-ascii-font-family:Consolas; mso-hansi-font-family:Consolas;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 75.1pt 1.0in 75.05pt; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.WordSection1 {page:WordSection1;} --> mingw32-make: *** No targets specified and no makefile found. Stop.
I also created a new file within this folder, and got the same result.
Posts: 2,698
Threads: 327
Joined: Apr 2022
Reputation:
217
Well, I can definitely say that's a new error type message for me! It's New Years right now -- HAPPY NEW YEARS -- and I imagine everyone is out celebrating for now, so it might be tomorrow (Monday) before anyone is awake and sober enough to look into the issue deeply. Give us a little patience and we'll see what we can sort out about what's happened for you. 
Posts: 35
Threads: 5
Joined: Apr 2022
Reputation:
5
(01-01-2023, 04:12 AM)PhilOfPerth Wrote: Help!!!
I've loused something up.
Suddenly I can't run any of my .bas progs (they've all run previously). I get message Failed to compile C++ on all of them.
I think it's something to do with where the compiled file is placed, but I can't see how to change this. In the Run menu, the option to Output to Source Folder is selected.
Happy new year.
Same for me many times when I download an update and extract it to the same folder.
Apparently some of the files are not replaced by the new ones.
Without being sure.
So I wipe the old install and unzip again, problem solved.
Gaslouk.
Posts: 652
Threads: 96
Joined: Apr 2022
Reputation:
22
01-01-2023, 08:56 AM
(This post was last modified: 01-01-2023, 09:09 AM by PhilOfPerth.)
(01-01-2023, 08:32 AM)gaslouk Wrote: (01-01-2023, 04:12 AM)PhilOfPerth Wrote: Help!!!
I've loused something up.
Suddenly I can't run any of my .bas progs (they've all run previously). I get message Failed to compile C++ on all of them.
I think it's something to do with where the compiled file is placed, but I can't see how to change this. In the Run menu, the option to Output to Source Folder is selected.
Happy new year.
Same for me many times when I download an update and extract it to the same folder.
Apparently some of the files are not replaced by the new ones.
Without being sure.
So I wipe the old install and unzip again, problem solved.
Gaslouk. Thanks Gaslouk. I'll give that a try - getting desperate now!
Edit:
Bingo! Removed all of the files ( saved my progs first) and re-extracted all again, and good as new! Thanks both.
Happy days!
And Happy New Year to all of youse.
Posts: 2,698
Threads: 327
Joined: Apr 2022
Reputation:
217
Here's my trick to happy QB64ing:
1) ALWAYS Download and extract into a new folder. C:\QB64\JAN01-2023\
2) Keep ALL my work in a separate folder. C:\QB64\My Stuff\
3) Keep others stuff in a separate folder. C:\QB64\Others Stuff\
4) Always click the OUTPUT EXE TO SOURCE option.
Now, when I download an updated version, or corrupt my old version of QB64PE, all I have to do is download and extract to a new folder. C:/QB64/JAN02-2023/
Click the OUTPUT EXE TO SOURCE FOLDER on the new installation, and I'm good to go! No need to move my stuff, or others stuff... just access it like I always did.
Posts: 3,978
Threads: 177
Joined: Apr 2022
Reputation:
220
Just so,
I even save old versions of QB64.exe. I have to rename them to get the new QB64.exe version registered with Windows so .bas files will run from latest version of QB64 with a single click from Files Browser.
b = b + ...
Posts: 135
Threads: 25
Joined: Apr 2022
Reputation:
39
Hello ! Happy New Year to everyone !
I once ran into such an error that the disk was full. it took me a long time to figure out why I was getting a "compile error" message. Do you have enough space on your drive?
Posts: 652
Threads: 96
Joined: Apr 2022
Reputation:
22
01-01-2023, 10:56 PM
(This post was last modified: 01-01-2023, 10:58 PM by PhilOfPerth.)
Yep, lotsa space. All fixed now thanks to post#5.
Will change to Steve's suggested filing method, though, for future security.
(well, with only one folder for .bas files, as I don't keep that many). 
|
