Re: [MiNT] FreeMiNT binaries and CPU specific versions

[Paul Wratt <paul.wratt@gmail.com>]

On Thu, Jul 28, 2011 at 7:09 AM, Jo Even Skarstein <joska@online.no> wrote:
> On Thu, 2011-07-28 at 05:05 +1200, Paul Wratt wrote:
>
>> hmm.. that may be easy enough to modify kernel source (1-18-cur +
>> 1-18-cur.???) but I think that still requires CVS to contain current
>> ??? build number somewhere.. which is painful..
>
> It doesn't have to do that. The nightly build (which I guess only runs
> if there has been any changes to the sources?) only have to increment
> the build-number after each successfull build. Remember that source
> version and build version is not the same. There can be many source
> versions between each build.
>
>> as for the other stuff, kernel an folder management, I have already
>> come up with a way under ARAnyM, using "ln -s" on both
>> "C:\mint\mint.prg" and "C:\mint\1-18-cur" and placing the actual
>> folders not in "C:\mint" where I was keeping them before. (btw same
>> technique works well with TOS/EmuTOS - both these scripts can be run
>> inside mint, then reboot)
>>
>> It is a bit trickier to do this under EasyMint because it uses TOS/FAT
>> boot drive and auto folder, but if I can get that to work, then it
>> will work on non-ARAnyM platforms too..
>>
>> after that it is just a matter of figuring a non-bash way to do the
>> same (for non-ARAnyM platform).. hmm might work if boot loader can set
>> SYSDIR when specific MINT.PRG is loaded.. we will see..
>
> There is one fundamental error with this approach: Scripts ;) Way to
> complex and s-l-o-w, and it's about as userfriendly as a square wheel.
> It's much easier with an optional loader in AUTO and the actual kernel
> in $SYSDIR. You don't have to mess with symlinks (which btw needs MiNT
> to work on a real machine, so the loader will never find $SYSDIR), the
> loader does everything for you without a single script or config-file.
>
> Jo Even
>
>
>
>

where is your working solution Jo?