ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: compiling project files
Date: Tue, 15 Aug 2006 16:29:10 -0400 (EDT)	[thread overview]
Message-ID: <Pine.WNT.4.63.0608151622390.3080@nqvgln> (raw)
In-Reply-To: <651881340608151316y77c9776fucd7f8ac8d2ff95ac@mail.gmail.com>

On Tue, 15 Aug 2006, Boris Tschirschwitz wrote:

> Let's say I have the following project structure
>
> project.tex
> env.tex
> product1.tex
>  component1.tex
>  component2.tex
> product2.tex
>
> Here, really, the whole project generates a single pdf at the end.
>
> Now, when working on component1, I would run
> $ texmfstart texexec project.tex
>
> Should I rather run texexec on product1.tex or component1.tex? Or maybe use
> texmfstart in some other way?

You should run texexec on prouct or component (not on the project)

> I am wondering about this because
> 1. Perter says
>   > Only components and products should be compiled.

Suppose you are typesetting a collection of books. Then project.tex 
should have common setup for all the books. product1.tex can be first 
book, product2.tex can be second book etc. component1.tex can be first 
chapter of the first book, etc. So, you are not supposed to compile 
the complete project.


> 2. When compiling projects that include MPgraphics, I have to run that
> texmfstart line
>   above twice to see changes to MPgraphics in my pdf. I thought 
that one
> idea behind
>   texexec is that it takes care of all incantations, like "make" in
> programming.
>


This should not happen.

Aditya
>
>
> On 8/14/06, Peter Münster <pmlists@free.fr> wrote:
>> 
>> On Sat, 12 Aug 2006, Derek Schmidt wrote:
>> 
>> > The .tuo file for the _product_ file shows the files being loaded.
>> > Compiling the _project_ file yields no .tuo. My product file does
>> > indeed look like what you wrote.
>> 
>> Hello Derek,
>> it's not intended to compile the project file. It should contain only
>> common setups for all products.
>> Only components and products should be compiled.
>> Cheers, Peter
>> 
>> --
>> http://pmrb.free.fr/contact/
>> _______________________________________________
>> ntg-context mailing list
>> ntg-context@ntg.nl
>> http://www.ntg.nl/mailman/listinfo/ntg-context
>> 
>

-- 
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008

  reply	other threads:[~2006-08-15 20:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09 15:52 Derek Schmidt
2006-08-09 16:26 ` Tobias Burnus
2006-08-09 16:27 ` Aditya Mahajan
2006-08-13  3:39   ` Derek Schmidt
2006-08-13 15:46     ` Mojca Miklavec
2006-08-14 20:44     ` Peter Münster
2006-08-15 20:16       ` Boris Tschirschwitz
2006-08-15 20:29         ` Aditya Mahajan [this message]
2006-08-16 15:58           ` Mojca Miklavec
2006-08-16 16:07             ` Taco Hoekwater
2006-08-16 22:52               ` 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=Pine.WNT.4.63.0608151622390.3080@nqvgln \
    --to=adityam@umich.edu \
    --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).