<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=GB2312" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks for your fast reply. I setup a info.ss file for ROOS and was able<br>
to create a package that works, using:<br>
<br>
(from the makfile:)<br>
<br>
<small><tt>planet: plt<br>
@echo "A collection package has been made to be distributed using
planet"<br>
<br>
#planet: scms docs precompile<br>
# $(PLANET) --create-archive $(PREFIX)/$(PACKAGE)<br>
<br>
<br>
plt: scms docs precompile<br>
$(MZC) --all-users --collection-plt roos-$(VERSION).plt roos<br>
#$(MZC) --collection-plt roos-$(VERSION).plt roos<br>
<br>
<br>
precompile:<br>
$(MZC) --cc c-roos.c<br>
$(MZC) --ld c-roos$(SHL) c-roos.obj<br>
mkdir -p $(PREFIX)/$(PACKAGE)/$(MZSCHEME_PRECOMP_DIR)<br>
cp c-roos$(SHL) $(PREFIX)/$(PACKAGE)/$(MZSCHEME_PRECOMP_DIR)<br>
<br>
collects: zos<br>
@if [ ! -d $(PREFIX)/roos ];then echo "Please install roos package
first";exit 1;fi<br>
$(MZC) --collection-extension roos<br>
<br>
zos: scms<br>
$(MZC) --collection-zos roos<br>
<br>
scms:<br>
mkdir -p $(PREFIX)/$(PACKAGE)<br>
cp roos.scm $(PREFIX)/$(PACKAGE)/roos.scm<br>
cp c-roos.c $(PREFIX)/$(PACKAGE)/c-roos.c<br>
cp c-roos.scm $(PREFIX)/$(PACKAGE)/c-roos.scm<br>
cp pre-installer.ss $(PREFIX)/$(PACKAGE)/pre-installer.ss<br>
cat info.ss | sed -e s/__VERSION__/$(VERSION)/g
>$(PREFIX)/$(PACKAGE)/info.ss<br>
<br>
docs:<br>
spod2html --indent-toc-with-spaces=4 --stylesheet=roos.css
doc/roos_manual.pod roos_manual.html<br>
mkdir -p $(PREFIX)/$(PACKAGE)/html<br>
cp roos_manual.html $(PREFIX)/$(PACKAGE)/html/index.html<br>
-dos2unix $(PREFIX)/$(PACKAGE)/html/index.html<br>
cp doc/style.css $(PREFIX)/$(PACKAGE)/html/roos.css<br>
cp doc.txt $(PREFIX)/$(PACKAGE)/doc.txt<br>
</tt></small><br>
<br>
However, <b>planet --create-archive <dir></b> doesn't seem to
generate a package that <br>
can be used to compile (or use the pre-compiled) c-roos.c.<br>
<br>
Another question: Is it advisable to (at least for WIN32) add a
pre-compiled variant<br>
of c sources or will they be mzscheme version specific?<br>
<br>
Thanks in advance for your answers,<br>
<br>
Hans Oesterholt-Dijkema<br>
<br>
<br>
Chongkai Zhu schreef:
<blockquote cite="mid20051227224225.5239815B55B@salt.cs.brown.edu"
type="cite">
<pre wrap="">_setup-extension.ss_
--------------------
[index entry: _Setup PLT compile extension_]
The "setup-extension.ss" library helps compile C code via Setup PLT's
"pre-install" phase (triggered by a `pre-installer' item in "info.ss";
see the "setup" collection for further information).
</pre>
<blockquote type="cite">
<pre wrap="">I believe that question was answered here before.
The answer is : YES.
Please refer to "Documentation for the Make collection" in the help
disk for details.
</pre>
<blockquote type="cite">
<pre wrap="">Hi all,
I recently posted a question about using PlaNET with C modules.
I'm not quite sure if it is supported or not. Can someone point
out if it is possible to include C parts in a planet package and
get it automatically compiled on requiring the planet package?
Thanks in advance for your answers,
Hans
</pre>
</blockquote>
<pre wrap="">
_________________________________________________
For list-related administrative tasks:
<a class="moz-txt-link-freetext" href="http://list.cs.brown.edu/mailman/listinfo/plt-scheme">http://list.cs.brown.edu/mailman/listinfo/plt-scheme</a>
</pre>
</blockquote>
<pre wrap=""><!---->
_________________________________________________
For list-related administrative tasks:
<a class="moz-txt-link-freetext" href="http://list.cs.brown.edu/mailman/listinfo/plt-scheme">http://list.cs.brown.edu/mailman/listinfo/plt-scheme</a>
</pre>
</blockquote>
<br>
</body>
</html>