[pb6.10b4] Required Compiler can't be found

[marcoagpinto]

Heya,

I decided to give it a try on PB 6.10 beta 4.

I keep getting this error when I try to compile:

[highend]

And you’ve checked the compiler settings of the current project you’re trying to compile?

[Mindphazer]

Uncheck "Use compiler" in the compiler options of your project.

[marcoagpinto]

Uncheck "Use compiler" in the compiler options of your project.

It worked!!!!!

But it is still a bug.

[Mindphazer]

Uncheck "Use compiler" in the compiler options of your project.

It worked!!!!!

But it is still a bug.

No bug. If you tell the IDE to compile with a compiler that is not present in the settings, it won't work.

[marcoagpinto]

Uncheck "Use compiler" in the compiler options of your project.

It worked!!!!!

But it is still a bug.

No bug. If you tell the IDE to compile with a compiler that is not present in the settings, it won't work.

I can't add it to the settings because selecting it with the file requester and pressing ADD doesn't work.

[marcoagpinto]

See the video of it not ADDING here:
https://www.youtube.com/watch?v=JdwsqiDgN2o

[ChrisR]

But it is still a bug.

No bug. If you tell the IDE to compile with a compiler that is not present in the settings, it won't work.

Um, I don't really agree. In the sense that you wrote it, Yes.
But new compilers should be updated in settings, when a new PB version is installed (with the same path).
And when a PB project or source is opened, the corresponding new compiler (C, Asm, x64, x86) should be updated as well, without checking the version number.

We shouldn't need to go back into the IDE and/or compiler's settings after installing a new version, no software does that!
If you open a project or source, on version 6.04 or 6.10, it should be ready to use, with the same configuration and no need to check it.

The current problem is that the check is made on the compiler name (with version inside) and not on the compiler path.
In the soure config: ; Compiler = PureBasic 6.01 LTS (Windows - x64)
In project : <compiler version="PureBasic 6.01 LTS - C Backend (Windows - x64)"/>

If it's not considered as a bug, it should at least be a feature request.
I had made a request here, for project

Edit: In your video, the C backend compiler is already added, it doesn't add it a 2nd time

[Quin]

Um, I don't really agree. In the sense that you wrote it, Yes.
But new compilers should be updated in settings, when a new PB version is installed (with the same path).
And when a PB project or source is opened, the corresponding new compiler (C, Asm, x64, x86) should be updated as well, without checking the version number.

We shouldn't need to go back into the IDE and/or compiler's settings after installing a new version, no software does that!
If you open a project or source, on version 6.04 or 6.10, it should be ready to use, with the same configuration and no need to check it.

The current problem is that the check is made on the compiler name (with version inside) and not on the compiler path.
In the soure config: ; Compiler = PureBasic 6.01 LTS (Windows - x64)
In project : <compiler version="PureBasic 6.01 LTS - C Backend (Windows - x64)"/>

If it's not considered as a bug, it should at least be a feature request.

+1. This gets incredibly annoying if you use C backend for everything, and have to go in and change it, every, time.

[marcoagpinto]

But it is still a bug.

No bug. If you tell the IDE to compile with a compiler that is not present in the settings, it won't work.

Um, I don't really agree. In the sense that you wrote it, Yes.
But new compilers should be updated in settings, when a new PB version is installed (with the same path).
And when a PB project or source is opened, the corresponding new compiler (C, Asm, x64, x86) should be updated as well, without checking the version number.

We shouldn't need to go back into the IDE and/or compiler's settings after installing a new version, no software does that!
If you open a project or source, on version 6.04 or 6.10, it should be ready to use, with the same configuration and no need to check it.

The current problem is that the check is made on the compiler name (with version inside) and not on the compiler path.
In the soure config: ; Compiler = PureBasic 6.01 LTS (Windows - x64)
In project : <compiler version="PureBasic 6.01 LTS - C Backend (Windows - x64)"/>

If it's not considered as a bug, it should at least be a feature request.
I had made a request here, for project

Edit: In your video, the C backend compiler is already added, it doesn't add it a 2nd time

I wasn't adding the C compiler, I was adding the normal compiler.

EDIT: The C compiler has an "c" in the filename, while the normal compiler doesn't.

[Mindphazer]

I can't add it to the settings because selecting it with the file requester and pressing ADD doesn't work.

Well. It's strangely not possible to add the ASM beta compiler, though it's possible to add LTS (C or ASM) compiler

[Mindphazer]

+1. This gets incredibly annoying if you use C backend for everything, and have to go in and change it, every, time.

The Default compiler is C backend in PB6.10 beta3 (and 4)

[Quin]

+1. This gets incredibly annoying if you use C backend for everything, and have to go in and change it, every, time.

The Default compiler is C backend in PB6.10 beta3 (and 4)

Wow! Even on Windows?
Was this documented somewhere?

[Fred]

Not on Windows or Linux, only for OS X and Raspberry.

[fryquez]

I wasn't adding the C compiler, I was adding the normal compiler.

You video show's that you adding the default compiler. But this option if only for additional compilers.
If you want to add PB 6.04, if have to install this version - to a different directory - and add the compiler from there.