[Lazarus] following wiki for new clean install from SVN...

[Marcos Douglas]

On Tue, Feb 8, 2011 at 10:13 PM, waldo kitty <wkitty42 at windstream.net> wrote:
>> I changed on the wiki.
>
> yes, i saw the note on another list about some changes...

Good.

>> Copy fpc.cfg script on the page... it works.
>
> i've done that and yes, it does work... however, the (buried) question is if
> the commandline's basepath= is incorrect...

See next answer...

>>> i've done this a couple of times and get the same error... however,
>>> fixing
>>> the paths in the fpc.cfg to remove the "\bin\i386-win32" portion put
>>> there
>>> by the above fpcmake command in 16a2 seems to fix this problem...
>>>
>>> is the fpcmkcfg command in 16a2 incorrect? should the basepath simply be
>>> "C:\freepascal\fpc\2.4.3" or will this cause other problems??
>>
>> I use the script on the page... the fpcmkcfg was included later (by
>> someone), but I not tested.
>
> ahhh... can you say if, as asked above, the basepath= portion is what is in
> error??

I don't know because I never use the fpcmkcfg tool!

> FYI: i'm looking to expand on the given instructions to include what is
> necessary to add cross compilation from OS whatever to OS something else...
> i hope that there's only a few minor changes needed... FPC is already placed
> into its own directory with an i386-win32 path... what would be needed to
> add i386-GO2V2 and i386-OS2 to the instructions? those are examples but are
> my target platforms so they serve as live examples :P

This places are to Win32 compilation. If you change the target, you
must be create another directories to the results.

>> Please, try again. I saw the wiki instructions. I think just the path
>> (\2.5.1 to \2.4.3) was wrong (before, at the first time, I used the
>> 2.5.1 compiler. After I changed to 2.4.3 and I forgot to change the
>> wiki... sorry).
>
> not a problem... as noted, i got thru it other than the fpcmkcfg commandline
> problem which i questioned originally... plus having the answers to
> adding/moving the example method to support crosscompiling with little
> modification other than holefully unzipping compiler X and libs Y would be a
> huge godsend ;)

I never used crosscompiling. I can't help you on this case, sorry.


Marcos Douglas