From jan@swi.psy.uva.nl Wed Sep 26 15:34:11 2001
Received: from gollem.swi.psy.uva.nl (root@gollem [145.18.152.30])
	by swi.psy.uva.nl (8.11.2/8.11.2) with ESMTP id f8QDYBv20288;
	Wed, 26 Sep 2001 15:34:11 +0200 (MET DST)
Received: from localhost (localhost [[UNIX: localhost]])
	by gollem.swi.psy.uva.nl (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id f8QDYAc18901;
	Wed, 26 Sep 2001 15:34:10 +0200
From: Jan Wielemaker <jan@swi.psy.uva.nl>
Organization: SWI, University of Amsterdam
To: Maniak-B <maniak-b@linuxbr.com.br>, <prolog@swi.psy.uva.nl>
Subject: Re: [SWIPL] Compiling an embedded engine, with gcc.
Date: Wed, 26 Sep 2001 15:29:12 +0200
X-Mailer: KMail [version 1.0.29.2]
Content-Type: text/plain
References: <Pine.LNX.4.33.0109060200280.29700-100000@spectroman.uol.com.br>
In-Reply-To: <Pine.LNX.4.33.0109060200280.29700-100000@spectroman.uol.com.br>
MIME-Version: 1.0
Message-Id: <0109261534100M.15353@gollem>
Content-Transfer-Encoding: 8bit

On Thu, 06 Sep 2001, Maniak-B wrote:
>Hi folks,
>
>I'm wondering why should I use plld instead of gcc ? Isnt the following
>line compatible with plld ?
>
>gcc -D__SWI_PROLOG__ -D__SWI_EMBEDDED__ -DREENTRANT -o test
>test-prolog.swi.o -g -lm -lreadline -ldl -lpl -L/usr/local/lib

Most likely on some platform.  Note however that plld also deals
with creating the saved-state if Prolog code is involved.  In
addition, it tries hide platform and Prolog configuration differences
to make it easy for you to write portable Makefiles.

Still, it is far from complete.  One of the plans is to hook in onto
the GNU libtool project, providing a very portable tool for embedding.
Given the differences between different OS and compiler/linker
configurations a truely portable solution is not easy though.

	--- Jan

