B b@s|dZdZddlZddlZddlZddlZddlZejj j Z dddZ dddZ ddd Z dadad d Zd d ZddZdS)zSCons.Tool.dvipdf Tool-specific initialization for dvipdf. There normally shouldn't be any need to import this module directly. It will usually be imported through the generic SCons.Tool.Tool() selection method. z,__FILE__ __REVISION__ __DATE__ __DEVELOPER__NcCsy|djj}Wntk r(d}YnXtjj|d|}||||}|tkrvy|dd=Wqtk rrYqXn ||dd<|S)zkA builder for DVI files that sets the TEXPICTS environment variable before running dvi2ps or dvipdf.rZTEXPICTSZENV) Z attributespathAttributeErrorSConsScannerLaTeXZmodify_env_var_nullKeyError)Z XXXDviActiontargetsourceenvabspathZ saved_envresultr0lib/python3.7/site-packages/SCons/Tool/dvipdf.pyDviPdfPsFunction+s   rcCstt|||}|S)N)r PDFAction)r r r rrrrDviPdfFunctionBsrcCs$|dr|dd||}nd}|S)zaA strfunction for dvipdf that returns the appropriate command string for the no_exec options.Zno_execz $DVIPDFCOMrr)Z GetOptionZsubst)r r r rrrrDviPdfStrFunctionFs rcs"ddfdd|D}||fS)zStrips any .aux or .log files from the input source list. These are created by the TeX Builder that in all likelihood was used to generate the .dvi file we're using as input, and we only care about the .dvi file. cSstjt|ddkS)N)z.auxz.log)rUtilsplitextstr)nrrrstrip_suffixesXsz"PDFEmitter..strip_suffixescsg|]}|r|qSrr).0src)rrr ZszPDFEmitter..r)r r r r)rr PDFEmitterRsrcCstdkrtjddatdkr.tjjttdaddlm}|||dd}| d t| d t d |d <tj d |d <d|d<dS)zEAdd Builders and construction variables for dvipdf to an Environment.Nz $DVIPDFCOMz $DVIPDFCOMSTR)Z strfunctionr)pdfZBUILDERSZPDFz.dvidvipdfZDVIPDFrZ DVIPDFFLAGSzFcd ${TARGET.dir} && $DVIPDF $DVIPDFFLAGS ${SOURCE.file} ${TARGET.file}Z DVIPDFCOM)rrZAction DVIPDFActionrrrrgenerateZ add_actionZ add_emitterrrZCLVar)r rZbldrrrr"]s     r"cCstjj||dS)Nr )rZToolZtexZgenerate_darwinZDetect)r rrrexistsrsr#)NNN)NNN)NNN)__doc__Z __revision__Z SCons.ActionrZSCons.DefaultsZSCons.Tool.pdfZSCons.Tool.texZ SCons.Utilrrrrrrrr!rr"r#rrrr s