Ok I can answer questions about the win32 how
to.
�
I had to change the line in glib.pp to read the
correct dll version from a 2 to a 3.
�

glibdll='glib-1.2';�
change to a 1.3 the latest version
glibdll='glib-1.3';�
�
I then compiled
�
ppc386 glib
ppc386 gtk
ppc386 gmodule
ppc386 gdk
�
copy the output .ow files to the units/win32 and overwrite the ones there.
�
The only example that will compile correct is the
notebook.pp
�
I did not use the make file to do this at all...
�
Cliff

I did not use the make file to do this at all...

Cliff,

You are ineed a giant among giants, but I am afraid that some of us may be a bit shorter in stature ;^)

What chance is there that there will be a way to get the make file to do this, or is it just an admission of guilt on my part that I just "don't get it"?

I must admit that 8 years of TP, BP and Delphi have kept me blissfully ignorant of makefiles in general, and that my C has been almost entirely limitted to subsets and non standard versions such as Echelon, that I find myself somewhat at a loss to figure out just what is going on.

I hope to use what skills I have aquired over the years to make this project a success, but I will need a few pointers on where to go from here. IDE life has left me somewhat lazy, but as always, I am ready to learn.

Should I be concentrating my efforts on learning make, rather than working on lazarus. If so, I am willing to do so. Because not everyone who wants to see this happen is a linux guru, and whether we are developing in win32 or not, the toolset provided is geared much more to those who have been used to the way linux operates.

Please don't take this as a flame in any way, because it is not. It is a desparate cry for help, to try to get the basics down, and move forward into being a useful contributor.

Jeff.

*********** REPLY PARTITION ***********

Peter Vreman wrote

Why that difficult? 'make install' would be enough to do this all for you if you've placed everything in /pp/source which is the default place since 0.99.12

I don't know why it is difficult. If I did, it wouldn't be difficult ;^) I created an \opt\fpc directory and ran CVS from there to get the source. I downloaded PPC386 and put it in \opt\fpc but nothing would compile. I downloaded the full '12 release of FPC, used it's install program tp install it to \opt\fpc. Then I could rebuild fpc by using "make cycle" but every time I tried to make anything else I got an error. I hadn't heard of "make install" before, but here is what happens at the end of when I do that...

...<snip>...
ppc386.exe -Twin32 -Xs -OG2p2 -n -Fue:\opt\fpc/rtl/win32 -Fue:\opt\fpc/units/win32 -di386 ppu.pas
Fatal: Can't compile unit SYSWIN32, no sources available make.exe[1]: *** [ppu.ppw] Error 1
make.exe[1]: Leaving directory `e:/opt/fpc/utils'
make.exe: *** [utils_install] Error 2

This is the same thing I get when I try to "make fpc" or "make gtk". Also, now that I have done that, I get an error when I try to rebuild the compiler that I didn't get before...

e:/opt/fpc/compiler/ppc3.exe -Twin32 -Fu../rtl/win32 -Fue:\opt\fpc/units/win32
-di386 -dSUPPORT_MMX -Sg -dGDB -dBROWSERLOG pp.pas mv -f pp.exe ppc386.exe
e:/opt/fpc/bin/win32/make.exe echotime
make.exe[4]: Entering directory `e:/opt/fpc/compiler' Start 10:15:04 now 10:19:03
make.exe[4]: Leaving directory `e:/opt/fpc/compiler' make.exe[3]: Leaving directory `e:/opt/fpc/compiler' make.exe[2]: Leaving directory `e:/opt/fpc/compiler' E:/OPT/FPC/BIN/WIN32/cmp.exe -i138 ppc3.exe ppc386.exe ppc3.exe ppc386.exe differ: char 537, line 4
make.exe[1]: *** [remake3] Error 1
make.exe[1]: Leaving directory `e:/opt/fpc/compiler' make.exe: *** [cycle] Error 2

I am lost. Maybe it is time to wipe everything out and start over...

Jeff.

*********** REPLY PARTITION ***********

since

Ok, I can't read... \pp\source eh? I see these directories but I didn't create them. So, am I supposed to run CVS checkout from the \pp\source directory? Do I change my path to point to \pp\bin\win32 instead of off of the \opt\fpc tree? I'll try it and see...

Jeff.

Ok Jeff I get your point how about I do something like this for you windows guys.

I will just layout my source directories and clean them up and make lazarus compile correctly.

I will then just zip it up and anyone wishing to do Lazarus coding can just unzip and get rolling. The only thing you would have to do is set the path property but I could make it do that also.

I will have it ready a little later this afternoon. As long as everyone uses the base fcl classes and the gtk dll's which will also be included the stuff will run on linux also. We will have to look at some of the issues with the code first thing such as the text being goofed up on the menus and such but that should be a easy fix.

What do ya think.

Cliff

Cliff

Why that difficult? 'make install' would be enough to do this all for you if you've placed everything in /pp/source which is the default place since 0.99.12

Cliff Baeseman wrote

I will just layout my source directories and clean them up and make

lazarus

compile correctly. I will then just zip it up and anyone wishing to do Lazarus coding can

just

unzip and get rolling. The only thing you would have to do is set the path property but I could make it do that also.

Actually I might could get by with just a copy of the directory tree structure (DIR /AD /S >dirtree.txt) from the home direcorty for FPC, and what PATH and SET variables you are using. I am sure that it is a simple thing I am missing, but I am frustrated.

Jeff.

Peter

Yep it probably would work but I needed to compile the modules individually to root out some of the problems..

Cliff