Author Topic: Working with IUP  (Read 13293 times)

0 Members and 2 Guests are viewing this topic.

JRS

  • Guest
Re: Working with IUP
« Reply #45 on: September 08, 2016, 10:14:50 AM »
FWIW, I have used 64 bit Windows IUP with Script BASIC 64 bit using TDMGCC 32/64. Using Microsoft's VC10 for 64 bit was a can of worms. IMO





« Last Edit: September 08, 2016, 11:16:53 AM by John »

Charles Pegge

  • Guest
Re: Working with IUP
« Reply #46 on: September 09, 2016, 02:14:36 AM »
Hi Roland,

To use the 64 bit DLLs You will need to compile your programs to independent 64bit EXEs, using RTL64.inc. The o2 dynamic run-time is limited to 32-bit, since oxygen.dll itself is 32bit

PS:

You will also need to remove cdecl from the extern statements.
« Last Edit: September 09, 2016, 02:36:50 AM by Charles Pegge »

Arnold

  • Guest
Re: Working with IUP
« Reply #47 on: September 09, 2016, 03:46:16 AM »
Hi Charles,

thank you. Now I understand. And creating an executable with RTL64.inc and commenting out the cdecl calling convention worked very fine. But before I continue trying out the 64bit possibilities, I will have to set up my Win 10 notebook a little bit. At the moment I feel uncomfortable with it.

Out of curiosity: as FreeBasic 1.05 exits for 64-bit systems too, would it be also possible to create oxygen.dll for x64 systems? I did not even try to spy at the source code of Oxygen, and I will not do this until I understand at least more of Oxygen's provided include files.

Roland

Charles Pegge

  • Guest
Re: Working with IUP
« Reply #48 on: September 10, 2016, 02:16:39 AM »
Hi Roland,

Yes, I think it would be possible to create a 64bit oxygen.dll using 64bit FB. This would require a complete rewrite of o2runt.bas and parts of o2hdrs.bas, and any other sections containing assembler.