From: Roman Schechtel <deepthinker@web.de>
Subject: Can't compile the whole project
Date: Tue, 13 Sep 2005 23:48:26 +0200 [thread overview]
Message-ID: <1714602375.20050913234826@web.de> (raw)
Hello from a new ConTeXt user!
I've read the wiki-page on how to separate input files into
a project structure (http://wiki.contextgarden.net/Project_structure)
and now I have the problem that:
- I can "compile" an individual component (resulting in a PDF)
- I also can compile a product
- But I can't compile the whole __project__!
Everytime I try to compile the project, I get the "No pages of
output" message in the log. My setup is the following:
----------------File: /environment.tex-------------------------
\startenvironment environment
\stopenvironment
----------------File: /project.tex-----------------------------
\startproject project
\environment environment
\product ./product/product
\stopproject
----------------File: /product/product.tex---------------------
\startproduct product
\project project
\component ./component/component
\stopproduct
----------------File: /product/component/component.tex---------
\startcomponent component
\product product
\project project
\dorecurse{10}{Component 1}
\stopcomponent
%________________________________________________________________
%I've put up those files in http://schechtel.de/pub/context/proj.zip
Now.. I get a PDF when I compile component.tex individually, the same
with product.tex -- but the PDF is not build when I compile
project.tex
The Logfile http://schechtel.de/pub/context/project.log.html
...shows something very interesting (marked red, scroll down).
What am I doing wrong?
Thanks for your help,
Roman Schechtel
next reply other threads:[~2005-09-13 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 21:48 Roman Schechtel [this message]
2005-09-14 6:26 ` Taco Hoekwater
2005-09-14 7:13 ` Wolfgang Zillig
2005-09-14 9:10 ` Roman Schechtel
2005-09-14 7:36 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1714602375.20050913234826@web.de \
--to=deepthinker@web.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).