PureBasic Forums - English

Hi everyone
I'd wish that paths to additional compilers (from older PB versions) are saved relativ to the PB directory,
because if you install PB on a USB storage with drive letter F: and then add some compilers
PB will not find these compilers if the USB storage gets another drive letter (i.e. G:).

Use the "/portable" command line switch to solve your issue. That's what it's for.

@Sirius-2337 +1

@MachineCode
/portable works only for relative paths, additional compilers stored with fixed paths

I mean have every version required (with whatever compiler) in its own folder, and then just use "/portable" when needed.

MachineCode wrote:I mean have every version required (with whatever compiler) in its own folder, and then just use "/portable" when needed.

This is a workaround, but not a good one: you can't use one IDE for all compilers then.

Why not just store the compilers in sub-directories inside the PB directory, then?

Zach wrote:Why not just store the compilers in sub-directories inside the PB directory, then?

Compilerpaths in Preferences are stored with fix path, so no difference.

Ohhh.. I misunderstood what was said.

But, is it still stored in a preference file or something that can be edited? Could try that route?

I tried to change the path to be relative to the PureBasic directory, but it didn't work.

External tools called from the "Tools" menu in the IDE are also not always portable. I've tested it several times on Windows XP x86, even now with PB 4.60 RC 1.

In the "Edit Tool Setting" window, a relative commandline only works if the respective program is located in a subdirectory of the PureBasic directory, e.g. But a relative commandline such as leads to an error, although notepad++.exe does exist at that location.

Regards, Little John