set compile output path

[circular17]

When I compile a sample project that uses BGRABitmap, it puts .o and .ppu files in the folder of BGRABitmap. I would like to choose the output path.

By the way the tab Make is artistic:

[fredvs]

I would like to choose the output path.

Add a line in Make option with -FUthediryouwant. For example If you use -FUunits, be sure that the directory units exists in the root directory of the main program file.

[fredvs]

By the way the tab Make is artistic:

Ooops, I have to fix font for that Project option window too.

OK, I will do asap.

[fredvs]

For BGRAbitmap directory, of course, when you are ready, I will add a global macro: ${BGRABITMAPDIR}, like it is for ${FPGUIDIR} and ${LCLDIR}.

[fredvs]

Totally out of the subject: you may try to compile with fpc-ootb based on fpc 3.2.0 R1. https://github.com/fredvs/freepascal-ootb/releases

If you use Windows or Linux, you may download the 32 and 64 bit releases. Unzip it somewhere, then with ideU, assign those 2 new compilers:

[circular17]

Add a line in Make option with -FUthediryouwant. For example If you use -FUunits, be sure that the directory units exists in the root directory of the main program file.

Perfect thanks!

[circular17]

I am testing fpc OOTB :)

[fredvs]

I am testing fpc OOTB :)

Brrrrr, I cross my fingers, it must be out of the box.

[circular17]

Relax I will tell you how it goes

[circular17]

Ok so how do I know if it uses the new compiler?

I have set the compiler 2 to be the 3.2.0 ootb.

Then how do I compile with it?

[fredvs]

When you have set the new compilers, see previous pictures, choose in the commandor panel the option number corresponding of the compiler you want to use and have set in project-options-compiler:

Then compile it clicking on the pink-compile icon.

[fredvs]

Then how do I compile with it?

See second picture from https://github.com/fredvs/ideU/issues/18#issuecomment-614736830

[circular17]

Oh ok somehow I missed the second window.

It works!

[fredvs]

It works!

Huh, was it out of the box?

[fredvs]

OOOps, if you try the 64 bit compiler on Windows, you should first upgrade MSEgui with last commit. There was a incompatibility with fpc 3.2.0 that was fixed yesterday.

[circular17]

Yep, I had nothing to do in the FPC folder.

I just struggled with configuring ideU.

Note I am on 32 bit Windows now.

[fredvs]

Ha ok, you dont have Windows 64 bit. What Windows version are you using?

[circular17]

Windows 7

[fredvs]

I did deep test on Windows 10 64 bit and did not see problems, after the patch of yesterday.

[circular17]

By patch you mean automatic update of Windows 10?

[fredvs]

By patch you mean automatic update of Windows 10?

No, the patch for MSEide-MSEgui to fix incompatibility with fpc >= 3.2.0 compiling a Windows 64 bit application.

[circular17]

I am confused, so the patch works?

[fredvs]

Yes the patch in last commit of msegui works: https://github.com/mse-org/mseide-msegui/commit/7e74e926bba5680b3e9f06616c5b9b3ed7c92f85

My develop machine uses Linux 64 bit and Wine the Windows emulator. But, to be sure, before to use Wine to create the release, the first time I check on a real Windows 10 machine if all is OK.

Yesterday I did try to compile some MSEgui applications with the brand new fpc-ootb Windows 64 bit and found some problems at compilation.

Note that before I never try to compile a MSEgui application with last fpc 3.2.0 RC1 64 bit, this simply because fpc does not provide a 64 bit release for Windows.

[circular17]

I see. Well all I can say is that on an old Windows 7 32-bit it works fine :-)

[fredvs]

I see. Well all I can say is that on an old Windows 7 32-bit it works fine :-)

Yep, perfect and I agree with you Windows 7 32-bit is the best Windows OS (after the Wine emulator, of course).

;)

[circular17]

Hehe Linux is the best ;-)

[fredvs]

By the way the tab Make is artistic:

Should be fixed in last commit b2b1f20

Fre;D

[circular17]

That's much better indeed