JEDI-SDL Full Installer...

[savage]

Hi all and in particular JEDI-SDL fans,
I know it's been ages and I keep saying that v1.0 is coming out soon ( sounding a bit like Duke Nukem Forever here ), but I finally put together an automated installer for Win32.
It can now be downloaded in 3 flavours :
FULL - http://jedi-sdl.pascalgamedevelopmen...LFullSetup.exe for testing purposes ( it's about a 4.5MB download ).
HEADERS ONLY - http://jedi-sdl.pascalgamedevelopmen...adersSetup.exe and it only about 1MB.
DEMOS ONLY - http://jedi-sdl.pascalgamedevelopmen...DemosSetup.exe and it only about 2MB.

It should install the files to the specified directory, but should also update your particular version of Delphi's Libaray path automagically. It should also update FreePascal's fpc.cfg if you used the FreePascal installer in the first place.

So it's not the official v1.0 release, but I am getting ever closer.

Please give it a test and let me know if there are any problems.

The JEDI-SDL home page @ http://jedi-sdl.pascalgamedevelopment.com has been updated with the URL to the installer as well.

Of the next few days I will be creating purely headers and pure demos versions of this installer.

If anyone has any experience in installing stuff for FreePascal on Win32 or Linux or MacOS X, please PM me.

[technomage]

nice one Dom.

I'll give it a go over the next day or so.

[arthurprs]

Downloaded

and spreading

[bigsofty]

Excellent stuff!

[savage]

Ok the new Headers and Full installations are now available for download and testing.

[arthurprs]

Ok the new Headers and Full installations are now available for download and testing.

Where i can find the changelog ?

[DarknessX]

Hey Savage check your PM's I sent you the solution for auto-magically installing to FPC

For those interested, here is an exact copy of the PM I sent him:

Well, I found what your looking for.

The fpc.cfg found in the C:\FPC\2.0.4\bin\i386 is NOT what you want. What you are looking for, is the fp.cfg. The other file, fpc.cfg, is really only an example file on how to edit the fp.cfg.

The file originally looks like this:

# Automaticly created file, don't edit.
#IFDEF NORMAL
 -TWin32
 -Sg
 -Mfpc
 -O1
 -OG
 -Op3
 -Ratt
 -FuC:\FPC\2.0.4\units\i386-Win32
 -FuC:\FPC\2.0.4\units\i386-Win32\*
 -FuC:\FPC\2.0.4\units\i386-Win32\rtl
 -g-
 -p-
 -b-
#ENDIF

#IFDEF DEBUG
 -TWin32
 -Sg
 -Mfpc
 -Cr
 -Ci
 -Co
 -OG
 -Op3
 -Ratt
 -FuC:\FPC\2.0.4\units\i386-Win32
 -FuC:\FPC\2.0.4\units\i386-Win32\*
 -FuC:\FPC\2.0.4\units\i386-Win32\rtl
 -g
 -p-
 -b-
#ENDIF

#IFDEF RELEASE
 -TWin32
 -Sg
 -Mfpc
 -O1
 -O2
 -OG
 -Op3
 -Ratt
 -FuC:\FPC\2.0.4\units\i386-Win32
 -FuC:\FPC\2.0.4\units\i386-Win32\*
 -FuC:\FPC\2.0.4\units\i386-Win32\rtl
 -g-
 -p-
 -b-
#ENDIF

But, as you can see, the ifdef's check the mode. So if you only want to use certain libs in certain modes, this is where you place them. When you are adding new items, you add them as seen below, but to change the type, change the switch before the directory. Example, for a unit, it is Fu.
For an Include (Inc) file, it is Fi, and for libraries and objects respectively, Fl and Fo. For an example, look below. The directories I added were:
//Units\\
C:\UNITS1
I:\MyUnits\UNITS2

//Inc Files\\
C:\INCLUDE FILES1
I:\INC FILES2

//Libs\\
C:\LIBRARIES
I:\Lib\LIBRARIES2

//Objects\\
C:\OBJECTS
I:\Obj\OBJECTS2

# Automaticly created file, don't edit.
#IFDEF NORMAL
 -TWin32
 -Sg
 -Mfpc
 -O1
 -OG
 -Op3
 -Ratt
 -FuC:\FPC\2.0.4\units\i386-Win32
 -FuC:\FPC\2.0.4\units\i386-Win32\*
 -FuC:\FPC\2.0.4\units\i386-Win32\rtl
 -g-
 -p-
 -b-
#ENDIF

#IFDEF DEBUG
 -TWin32
 -Sg
 -Mfpc
 -Cr
 -Ci
 -Co
 -OG
 -Op3
 -Ratt
 -FuC:\FPC\2.0.4\units\i386-Win32
 -FuC:\FPC\2.0.4\units\i386-Win32\*
 -FuC:\FPC\2.0.4\units\i386-Win32\rtl
 -FuC:\UNITS1
 -FuI:\MyUnits\UNITS2
 -FiC:\INCLUDE FILES1
 -FiI:\INC FILES2
 -FlC:\LIBRARIES
 -FlI:\Lib\LIBRARIES2
 -FoC:\OBJECTS
 -FoI:\Obj\OBJECTS2
 -g
 -p-
 -b-
#ENDIF

#IFDEF RELEASE
 -TWin32
 -Sg
 -Mfpc
 -O1
 -O2
 -OG
 -Op3
 -Ratt
 -FuC:\FPC\2.0.4\units\i386-Win32
 -FuC:\FPC\2.0.4\units\i386-Win32\*
 -FuC:\FPC\2.0.4\units\i386-Win32\rtl
 -g-
 -p-
 -b-
#ENDIF

Note that they are only in the Debug section, which is because of the compile mode, set in the fp.ini file located in the same directory, is normally set to Debug during production. If the mode is changed, the libraries are no longer accessible...

[code="fp.ini"]
[Compile]
CompileMode=DEBUG <----- I switched this to release, and I could no longer access the edits.

[Editor]
DefaultTabSize=8
DefaultFlags=20599
[/code]

[savage]

As mentioned :

This helps, but still does not address the issue of finding this particular file in a consistent way for all FreePascal users, so that it can be edited. Scanning the whole HD during the installation seems unacceptable to me.

Also Is the change from using fpc.cfg to fp.cfg something new to FreePascal? In the past I always added the paths manually to fpc.cfg.

[DarknessX]

It might be, but over much experimentation, I found the fpc.cfg file was nothing more than an example file... Mind you, I could be completely wrong, but when I added new units via FPC's internal Directories... option, it was added to the fp.cfg, and not fpc.cfg.

# Config file generated by fpcmkcfg on 8/11/2007 - 3:59
# Example fpc.cfg for Free Pascal Compiler

Thats what is shown at the top of my fpc.cfg file... So it is quite likely that you can add it to fpc.cfg aswell, and without as much hassle... I just never knew it

[technomage]

This line at the top of the fp.cfg file states you should not edit the file.

# Automaticly created file, don't edit

Adding the lines to fpc.cfg is correct.