compiling project files

compiling project files

[Derek Schmidt]

Hi there,

I'm a complete ConTeXt newbie, so please be patient with me. :)

I'm putting together a book and I'm trying to use the project
structure that Context likes so much. My components come out
beautifully--they are chapters in the book.

The product file is the actual book. I don't have the code in front of
me, but it looks very much like the examples given in the manuals and
at ContextGarden. When I texexec it, it runs but only produces and
empty table of contents with the word Contents at the top. It won't
list the chapters, forget about actually printing their content.

Any ideas on what I'm doing wrong? I'm guessing this might not be
enough info for you to help. I'll try to answer any questions as best
I can.

Thanks and

all best,
Derek

Re: compiling project files

[Tobias Burnus]

Hi Derek,

Derek Schmidt wrote:
> When I texexec it, it runs but only produces and empty table of contents with the word Contents at the top. It won't list the chapters, forget about actually printing their content.
>   
I have only three ideas:

(a)  The data is not available. The mechanism is a follows:
1. TeX is run and chapter names with pagenumbers etc. are saved into
<jobname>.tui.
2. TeXutil is run and sorts some entries in *.tui and writes *.tuo
3. TeX is run again, reads .tuo and uses that data to produce the table
of contents etc. (and produces a new .tui)
As this changes the page numbers (for longer table of contents), TeXutil
and TeX are re-run again.
In principle TeXExec should do this automatically. Do you have a *.tuo file?

(b) The data is available via .tuo but somehow \completecontent only
writes the sections below the "Content" chapter, which is empty.
Try:  \completecontent[criterium=all]
this instructs it to print the table of content for all chapters (which
is actually the default).

(c) Something is broken (whatever, the installation, ConTeXt/TeXexec, my
ability to find the cause of problems etc.)

Tobias

Re: compiling project files

[Aditya Mahajan]

On Wed, 9 Aug 2006, Derek Schmidt wrote:

> Hi there,
>
> I'm a complete ConTeXt newbie, so please be patient with me. :)
>
> I'm putting together a book and I'm trying to use the project
> structure that Context likes so much. My components come out
> beautifully--they are chapters in the book.
>
> The product file is the actual book. I don't have the code in front of
> me, but it looks very much like the examples given in the manuals and
> at ContextGarden. When I texexec it, it runs but only produces and
> empty table of contents with the word Contents at the top. It won't
> list the chapters, forget about actually printing their content.

I do not understand this. Do you mean that the components are not in 
the output?


> Any ideas on what I'm doing wrong? I'm guessing this might not be
> enough info for you to help. I'll try to answer any questions as best
> I can.

It is pretty hard to guess. Does your product file look like this

\startproduct product-name

\environment env-name

\component component-1
\component component-2
....

\stopproduct


Maybe the components are not getting loaded. To actually see which 
files are being loaded, look at product.tui file. The enteries 
starting with f tell you which files are being read. What does the 
output of

grep "^f" product.tui

look like?

Aditya

Re: compiling project files

[Derek Schmidt]

Aditya,

Sorry it took so long to get back to you. I've only just had a chance
to try this now.

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.

Shall I jump out the window or not? :)

--Derek

On 8/9/06, Aditya Mahajan <adityam@umich.edu> wrote:
> On Wed, 9 Aug 2006, Derek Schmidt wrote:
>
> > Hi there,
> >
> > I'm a complete ConTeXt newbie, so please be patient with me. :)
> >
> > I'm putting together a book and I'm trying to use the project
> > structure that Context likes so much. My components come out
> > beautifully--they are chapters in the book.
> >
> > The product file is the actual book. I don't have the code in front of
> > me, but it looks very much like the examples given in the manuals and
> > at ContextGarden. When I texexec it, it runs but only produces and
> > empty table of contents with the word Contents at the top. It won't
> > list the chapters, forget about actually printing their content.
>
> I do not understand this. Do you mean that the components are not in
> the output?
>
>
> > Any ideas on what I'm doing wrong? I'm guessing this might not be
> > enough info for you to help. I'll try to answer any questions as best
> > I can.
>
> It is pretty hard to guess. Does your product file look like this
>
> \startproduct product-name
>
> \environment env-name
>
> \component component-1
> \component component-2
> ....
>
> \stopproduct
>
>
> Maybe the components are not getting loaded. To actually see which
> files are being loaded, look at product.tui file. The enteries
> starting with f tell you which files are being read. What does the
> output of
>
> grep "^f" product.tui
>
> look like?
>
> Aditya
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>

Re: compiling project files

[Mojca Miklavec]

On 8/13/06, Derek Schmidt wrote:
> Aditya,
>
> Sorry it took so long to get back to you. I've only just had a chance
> to try this now.
>
> 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.
>
> Shall I jump out the window or not? :)

It depends on which floor you live in ;)

It might help if you create a *minimal* example first (just a few
files with no more than the structure itself and a couple of
words/sections in it), write the commands that you use and attach a
zip with those files and probably logs.

Mojca

PS: try to update ConTeXt to the latest version if you intend to send
log files and try to use the ruby version of texexec ("texmfstart
texexec") if possible. None should be necessary (it should work with
the ancient version as well), but it often helps, esp. because tetex
still uses the "2002" version of ConTeXt for example.

Re: compiling project files

[Peter Münster]

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/

Re: compiling project files

[Boris Tschirschwitz]

[-- Attachment #1.1: Type: text/plain, Size: 1480 bytes --]

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?

I am wondering about this because
1. Perter says
    > Only components and products should be compiled.
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.

Cheers,
Boris.


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
>

[-- Attachment #1.2: Type: text/html, Size: 2059 bytes --]

[-- Attachment #2: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: compiling project files

[Aditya Mahajan]

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

Re: compiling project files

[Mojca Miklavec]

On 8/15/06, Aditya Mahajan wrote:

> > 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.

I agree with the fact that it should not happen, but it does (perhaps
I should say "did", because the last time when I had the problem was
once in May; a whole lot of changes have been made since then and I'm
not sure if I can find the file which caused me problems again).

Can you send a minimal example?

Mojca

Re: compiling project files

[Taco Hoekwater]

Mojca Miklavec wrote:
> On 8/15/06, Aditya Mahajan wrote:
> 
> 
>>>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.
> 
> 
> I agree with the fact that it should not happen, but it does (perhaps
> I should say "did", because the last time when I had the problem was
> once in May; a whole lot of changes have been made since then and I'm
> not sure if I can find the file which caused me problems again).

IIRC, this problem only crops up when \runMPgraphicstrue is not set
(so that mpost is run by texexec between TeX runs)

Taco

Re: compiling project files

[Hans Hagen]

Taco Hoekwater wrote:
> Mojca Miklavec wrote:
>   
>> On 8/15/06, Aditya Mahajan wrote:
>>
>>
>>     
>>>> 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.
>>>       
>> I agree with the fact that it should not happen, but it does (perhaps
>> I should say "did", because the last time when I had the problem was
>> once in May; a whole lot of changes have been made since then and I'm
>> not sure if I can find the file which caused me problems again).
>>     
>
> IIRC, this problem only crops up when \runMPgraphicstrue is not set
> (so that mpost is run by texexec between TeX runs)
>   
normally checksums are made; i must see the failing example 

Hans 

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------