Hi Christian,
yeah I got the same error as you and I tried once doing step b) but
since I have to compile the document quite often this got frustrating
when I cleaned my environment once in a while ;-)
I guess for the moment I will use the trick which Stefan told me
(disabling and enabling externalization).
Thanks for your help. I will have a look at the manual section 7
(+ TikZ) for more insights.
Regards,
Stefan
On Mo, 2010-10-11 at 11:03 +0200, Christian Feuersänger wrote:
> Hi Stefan,
>
> your example can be externalized successfully.
>
> It only requires a special way to do so: when I compile the document
> (it is called "P.tex") with
> pdflatex -shell-escape P
> I get
>
> ! Package tikz Error: Sorry, the system call 'pdflatex -shell-escape
> -halt-on-error -interaction=batchmode -jobname "P-figure_crossref0"
> "\def\tikzexternalrealjob{P}\input{P}"' did NOT result in a usable
> output file 'P-figure_crossref0' (expected one
> of .pdf:.jpg:.jpeg:.png:). Please verify that you have enabled system
> calls. For pdflatex, this is 'pdflatex -shell-escape'. Sometimes it is
> also named 'write 18' or something like that. Or maybe the command
> simply failed? Error messages can be found in
> 'P-figure_crossref0.log'. If you continue now, I'll try to typeset the
> picture.
>
> The file P-figure__crossref0.log contains more details:
> ! Package tikz Error: Sorry, image externalization failed: the
> resulting image was EMPTY. I tried to externalize
> 'P-figure_crossref0', but it seems there is no such image in the
> document!?
> You are currently using 'mode=convert with system call'. This
> problem can happen if the image (or one of the images preceeding it)
> was declared inside of a \label{} (i.e. in the .aux file): 'convert
> with system call' has no access to the main aux file.
> Possible solutions in this case:
> a) Try using 'mode=list and make',
> b) Issue the externalization command 'pdflatex -shell-escape
> -halt-on-error -interaction=batchmode -jobname "P-figure_crossref0"
> "\def\tikzexternalrealjob{P}\input{P}"' *manually* (also check the
> preceeding externalized images, perhaps the file name sequence is not
> correct).
> Repeat: the resulting image was EMPTY, your attention is required .
>
> I chose to follow the advice of step (b), afterwards everything
> worked.
>
> You can find background details concerning this stuff in the manual,
> Section 7 "Import/Export From Other Formats" in paragraph "Support for
> Labels and References In External Files". The tikz developer version
> manual also contains (perhaps even more detailed) information about
> the externalization.
>
> The steps above rely on a recent pgfplots version (I used pgfplots
> 1.4.1 or, more precisely, the unstable dev version on top of it).
>
> I hope this helps you. If not, it would help if you could post the log
> file(s) of your minimal example as well.
>
> Best regards
>
> Christian
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
> Spend less time writing and rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________ Pgfplots-features mailing
> list Pgfplots-features@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pgfplots-features
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Pgfplots-features mailing list
Pgfplots-features@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pgfplots-features
