[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] Compiling a FreeMiNT kernel

To: mint@lists.fishpool.fi
Subject: Re: [MiNT] Compiling a FreeMiNT kernel
From: Vincent Rivière <vincent.riviere@freesbee.fr>
Date: Sat, 12 Oct 2013 14:04:01 +0200
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=U3dSFCw7spAa+BE8R2xXrj9IHczvS5LcVoTeaeNiJPI=; b=hOO6g4SVbXSDKbUiPxQYByvcfKdS0o+9ox588snyrHcQvoRGJphsV4F8QBp8HqGIXz QIoGjvxmeexUdf4wBINmGCHzb809BjMdlYRrMp17if99l0J8u6nQ+mNIyG050ddgBaFM wVBNcVb1PTP0LZ4dsRR67MbMbFgIbL5YQfYDBE8cfxF2dp76ERu6FtAkG023HrFgjKYH aIsC7lATNfMQPVq8LznkSuuvU7/Tlle5YM1PY79OsCpPxS9jmCKlsDqMNicSXV1CC6nW iF3hxO5Xh9Sw98G7bgIObHp6trsPyS9y7Xlg3GQ5RoNimr69PsJXkMB5X+zOAOS9DqxB eJBA==
In-reply-to: <1381568676.2599.5.camel@jll>
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-id: <mint.lists.fishpool.fi>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
References: <1381419194.2583.6.camel@jll> <EB5BA03A-3411-4F14-BDAB-1C480B7E6E1A@mubf.de> <1381516637.2573.7.camel@jll> <CAN5rfbSpmcO4Muf_m-UvFXfFW6fO=m9TvULTgTZR3VM+a8iOpw@mail.gmail.com> <1381568676.2599.5.camel@jll>
Sender: mint-bounce@lists.fishpool.fi
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1

On 12/10/2013 11:04, Matthias Arndt wrote:

Now I just wonder why the compiled kernel .prgs are in hidden
directories while all drivers are directly insitu with their sources?


There are 2 different approaches:

1) The kernel: the same sources are built multiple times to producedifferent kernel variants. This is why the binaries are generated insubdirectories, which, surprisingly, are hidden (starts with a dot).

2) The tools and kernel modules: they are built just once for 68000, somultiple subdirectories are not required.


The FreeMiNT source tree has become quite a mess.

A long lasting project is to rework the makefiles and build process, toenable building everything for a specific CPU and/or machine.

As a result, currently I need to use a custom build script to compileeverything optimized for ColdFire:

http://vincent.riviere.free.fr/soft/m68k-atari-mint/archives/mint/freemint/freemint-1.18.0-bin-firebee.sh

--
Vincent Rivière

Follow-Ups:
- Re: [MiNT] Compiling a FreeMiNT kernel
  - From: Matthias Arndt <marndt@asmsoftware.de>

References:
- [MiNT] Compiling a FreeMiNT kernel
  - From: Matthias Arndt <marndt@asmsoftware.de>
- Re: [MiNT] Compiling a FreeMiNT kernel
  - From: Markus Fröschle <markus@mubf.de>
- Re: [MiNT] Compiling a FreeMiNT kernel
  - From: Matthias Arndt <marndt@asmsoftware.de>
- Re: [MiNT] Compiling a FreeMiNT kernel
  - From: Miro Kropáček <miro.kropacek@gmail.com>
- Re: [MiNT] Compiling a FreeMiNT kernel
  - From: Matthias Arndt <marndt@asmsoftware.de>

Prev by Date: Re: [MiNT] [Mint-cvs] [FreeMiNT CVS] freemint/sys
Next by Date: Re: [MiNT] [Mint-cvs] [FreeMiNT CVS] freemint/sys
Previous by thread: Re: [MiNT] Compiling a FreeMiNT kernel
Next by thread: Re: [MiNT] Compiling a FreeMiNT kernel
Index(es):
- Date
- Thread