32bit or 64bit for compatibility?

[MachineCode]

Now that I have Win 7 (64bit), should I using the 64bit version of PureBasic? Will the exes created by it work on XP (32bit) though?

[luis]

Now that I have Win 7 (64bit), should I using the 64bit version of PureBasic? Will the exes created by it work on XP (32bit) though?

The x64 version of PB generate only x64 code, so the exe work on 64 bit OS only.
You can install both versions on the same machine.
Both IDEs can invoke both the compilers though, so you can use one IDE to generate 32 and 64 bit programs, provided you have both compilers installed.

[MachineCode]

Thanks Luis, I'll just use the 32bit PureBasic so I don't have to think about anything.

[jack]

has anyone installed both version of PB on the same machine?
I would like to know the steps required so as not to have conflicts between the two.

[Zebuddi123]

Hi Install both versions. In "preferences\compiler" select the 64|32 bit compiler from the file requester, "C:\Program Files (86)\PureBasic\Compilers"|"C:\Program Files\PureBasic\Compilers" depending on whether your using 32|64 bit IDE and click "add"

When compiling select the target OS 32|64 bit.

Dont forget that there are more userlibs compiled as 32 bit than 64 bit, so make sure you have 64 bit version of the 32 bit userlibs you use if available and install them in the 64 bit userlibs directory.

Zebuddi.

[jack]

thank you Zebuddi

[NoahPhense]

Is this the best way to have both versions installed? I prefer to only keep 64bit installed. But if the need occurs, I would like to be able to push to a 32bit machine.

Would be nice if the 64bit version came with the 32bit compiler. For ease of use.

- np

[dobro]

2 versions =

a folder 5.42 Pb / .... and inside:


1 - Pb 5.42 / X86 / <--- Pb install 32 bit here
1- Pb 5.42 / X64 / <--- Pb install 64 bit here

and for each version of Purebasic

at Home :

for any Pb version : (no in Program_file , but in a personalized folder of partition D:\..


sample in Pb 5_20 folder :


in x64 Folder (Pb 64 bits )


in x86 Folder (Pb 32 bits )


and this for All Version

[NoahPhense]

Ok, that helps. I will probably do:

c:\pb\32\
c:\pb\64\

Versions don't matter to me, I always use the most recent (beta or full). Plus it helps with the paths and such.

My follow-up question would be, regarding the userlibs as already mentioned in this thread. Any tips on that?

Cheers!

- np

[dobro]

c:\pb_5_42\32\
c:\pb_5_42\64\

c:\pb_5_5\32\
c:\pb_5_5\64\

believe me, I advise you to name the version number, just because
because of userLibrairies, that will not necessarily updates ...

I'm sure if you develloppes with PB5.42
when will last a PB 5.5, you will still need to 5.42 PB ...
for several reasons
I think: compatibilitée user libraries
future bugs Version 5.5
and syntax changes, which requires a whole re-write a list (more than 16000 lines read)

I advise you to never use a library user, if you do not have the source code!

otherwise, proceeding with a version by folder, each folder of Librairie, is in

[NoahPhense]

I will keep older versions of PB, I just wont install them unless there is large need for them. When ever I have major edits to source code, usually to bring the app current. I break out Sublime Text 3.

My main concern about installing multiple versions of PB, is whether or not it would create any havoc within the registry.

Thanks again for the info.

Cheers!

- np

[Thunder93]

...create any havoc within the registry.

It won't it'll keep updating with the latest PB information, unless you installing a previous version.

[NoahPhense]

...create any havoc within the registry.

It won't it'll keep updating with the latest PB information, unless you installing a previous version.

Excellent, thanks.

Currently running: PureBasic 5.50 beta 1 (Windows - x64) Just need to get x86 running along side it for all those 32bit machines still out there.

- np

[NoahPhense]

c:\pb_5_42\32\
c:\pb_5_42\64\

c:\pb_5_5\32\
c:\pb_5_5\64\

OK, I've changed (my mind) my setup as such:

C:\pb\5_50\32\
C:\pb\5_50\64\

Then, after 5.50 goes LTS, I will start a new install with whatever beta comes next, say:

C:\pb\5_52\32\
C:\pb\5_52\64\

I don't really want to indicate beta or LTS within the file path.

What do you think about this approach?

- np

[Demivec]

Then, after 5.50 goes LTS, I will start a new install with whatever beta comes next, say:

C:\pb\5_52\32\
C:\pb\5_52\64\

I don't really want to indicate beta or LTS within the file path.

What do you think about this approach?

There won't be a v5.50 LTS. Because it has added functions since the last LTS it will simply be v5.50 when it's released. Any fixes will be applied to the LTS and released as v5.43 LTS.

Here's how I treat the beta releases.

Following the pattern already shown I use these folders:

Code: Select all

C:\pb\beta\32\
C:\pb\beta\64\

I install them in the corresponding directory, overwriting any previous installation. This allows me to set up a shortcut to launch them that will always run the most recent beta. After the release is finalized the beta is never used until the next version is tested.


Withe both the final releases and the beta versions, I execute them with the '\PORTABLE' switch. This stores their settings in the directories where they are executed from and prevents different versions from conflicting with each other. Any user preferences can be migrated from previous versions.