@K7]c@`s)ddlmZmZmZddlmZddlZddlZddlZddl Z ddl Z ddl Z ddl m Z ddlmZddlmZmZmZmZmZddlmZdd lmZmZmZmZdd lmZdd lm Z dd l!m"Z"d e j#fdYZ$de j%fdYZ&de'de)dZ*de'de)dZ+dZ,e'de)dZ-ia.dddde'e'e'dZ/e'dZ0dde'e'e'e'dZ1dZ2e'dZ3e'dZ4e'e'dZ5e'e'e'ddZ6dS( i(tabsolute_importtdivisiontprint_function(tpartialNi(tPY3(tget_dict(tget_installed_packagestapply_pin_expressionst get_loggert HashableDictt string_types(tget_env_dependencies(t copy_intotcheck_call_envtrm_rftensure_valid_spec(tDEFAULT_COMPILERS(tCondaBuildException(t_load_setup_py_datatUndefinedNeverFailcB`seZdZgZd ejjd ejj dZ dZ Z Z ZZZZZZZZZZZZZZZZZZZ Z!dZ"dZ#Z$dZ%dZ&dZ'dZ(d Z)d d Z*RS( s A class for Undefined jinja variables. This is even less strict than the default jinja2.Undefined class, because it permits things like {{ MY_UNDEFINED_VAR[:2] }} and {{ MY_UNDEFINED_VAR|int }}. This can mask lots of errors in jinja templates, so it should only be used for a first-pass parse, when you plan on running a 'strict' second pass later. Note: When using this class, any usage of an undefined variable in a jinja template is recorded in the (global) all_undefined_names class member. Therefore, after jinja rendering, you can detect which undefined names were used by inspecting that list. Be sure to clear the all_undefined_names list before calling template.render(). cC`s tjj|||||dS(N(tjinja2t Undefinedt__init__(tselfthinttobjtnametexc((s8lib/python2.7/site-packages/conda_build/jinja_context.pyR(scO`s|j|jS(N(t_return_undefinedt_undefined_name(Rtargstkwargs((s8lib/python2.7/site-packages/conda_build/jinja_context.pyt3tcC`sDytj||SWn)tk r?|j|jd|nXdS(Nt.(tobjectt __getattr__tAttributeErrorRR(Rtk((s8lib/python2.7/site-packages/conda_build/jinja_context.pyR$7s cC`s|jtS(N(t _return_valuetstr(R((s8lib/python2.7/site-packages/conda_build/jinja_context.pyR ?R!cC`s |jdS(Nu(R'(R((s8lib/python2.7/site-packages/conda_build/jinja_context.pyR @R!cC`s |jdS(Ni(R'(R((s8lib/python2.7/site-packages/conda_build/jinja_context.pyR AR!cC`s |jdS(Ng(R'(R((s8lib/python2.7/site-packages/conda_build/jinja_context.pyR BR!cC`s |jtS(N(R'tFalse(R((s8lib/python2.7/site-packages/conda_build/jinja_context.pyR CR!c C`s;tjj|jtd|jd|jd|d|jS(NRRRR(Rtall_undefined_namestappendRt_undefined_hintt_undefined_objt_undefined_exception(Rt result_name((s8lib/python2.7/site-packages/conda_build/jinja_context.pyREs  cC`stjj|j|S(N(RR*R+R(Rtvalue((s8lib/python2.7/site-packages/conda_build/jinja_context.pyR'MsN(+t__name__t __module__t__doc__R*tNoneRtruntimetmissingt exceptionstUndefinedErrorRt__add__t__radd__t__mul__t__rmul__t__div__t__rdiv__t __truediv__t __rtruediv__t __floordiv__t __rfloordiv__t__mod__t__rmod__t__pos__t__neg__t__call__t __getitem__t__lt__t__le__t__gt__t__ge__t __complex__t__pow__t__rpow__R$t__str__t__repr__t __unicode__t__int__t __float__t __nonzero__RR'(((s8lib/python2.7/site-packages/conda_build/jinja_context.pyRs a       tFilteredLoadercB`s eZdZdZdZRS(s A pass-through for the given loader, except that the loaded source is filtered according to any metadata selectors in the source text. cC`s"||_|j|_||_dS(N(t_unfiltered_loadertlist_templatestconfig(Rtunfiltered_loaderRY((s8lib/python2.7/site-packages/conda_build/jinja_context.pyRYs  cC`seddlm}m}|jj||\}}}||||jdt|jj||fS(Ni(t select_linestns_cfgtvariants_in_place(tmetadataR[R\RWt get_sourceRYtbooltvariant(Rt environmentttemplateR[R\tcontentstfilenametuptodate((s8lib/python2.7/site-packages/conda_build/jinja_context.pyR_^s  (R1R2R3RR_(((s8lib/python2.7/site-packages/conda_build/jinja_context.pyRVSs ssetup.pyc C`sd}tjjtjjtd}tjj|jjd}t||t |}d|ds Rt__iter__is>=t,s<{upper_bound}t upper_boundspin_compatible\s*\(\s*["]{}["]s]Could not get compatibility information for {} package. Is it one of your host dependencies?N(RR RYRatcached_env_dependenciestis_crosst build_is_hostR RwtgetRpthasattrt isinstanceR R(RRRtcompileRtextract_requirements_textRR4(Rt package_namet lower_boundRtmin_pintmax_pinRmtexacttbypass_env_checkt compatibilitytkeytpinst_t host_pinstversionstversiontcheck((s8lib/python2.7/site-packages/conda_build/jinja_context.pytpin_compatibles@   $! !     c `s~d}|rzt|dkr+|d} nt|dkrd} xu|D]j\} tjtjjj@} | stfd| DrJ| f} PqJqJWn| |kri|| d} |r| j rd}qw|r<dj| j | j|s!| j nt | j g}qwdj | j t| j||}qz|dd}n|S(Niic3`s)|]}|jj|kVqdS(N(RYRa(Rtsv(R^Ra(s8lib/python2.7/site-packages/conda_build/jinja_context.pys sRs{0} {1}(R4tlentsettkeysRYRatallRRpRtbuild_idR(t build_numberRR( R^tmatching_package_keystoutputsRRRRmt skip_build_idtpinRtpkg_namet shared_varstsp_m((R^Ras8lib/python2.7/site-packages/conda_build/jinja_context.pytpin_subpackage_against_outputss0 (     -c C`sd}t|ds3|r$|}qtdnet|jj} g| D]} | d|krO| ^qO} t|| |j||||d|}|s|}| r| rtdj|qn|S(sallow people to specify pinnings based on subpackages that are defined in the recipe. For example, given a compiler package, allow it to specify either a compatible or exact pinning on the runtime package that is also created by the compiler package recipe t other_outputssoBug in conda-build: we need to have info about other outputs in order to allow pinning to them. It's not here.iRsDidn't find subpackage version info for '{}', which is used in a pin_subpackage expression. Is it actually a subpackage? If not, you want pin_compatible instead.N(R4Rt ValueErrortlistRRRR( R^tsubpackage_nameRRRRmtallow_no_other_outputsRRRR&R((s8lib/python2.7/site-packages/conda_build/jinja_context.pytpin_subpackage.s" )     cC`s|}xQ|j|jjddgD]0}yt||}PWq&tk rUq&q&Xq&Wt|dr|j|jjddd}n|S(Nt-iRtpythontnopetvs2017(tplatformRRtKeyErrorRRRa(tlanguageRYtcompilerR((s8lib/python2.7/site-packages/conda_build/jinja_context.pytnative_compilerQs&  $cC`st||}d}|jrs|jjd|j}dj|}|jj||}|jj|d}n |j}dj||g}|rdj||f}t|dt}n|S(s{Support configuration of compilers. This is somewhat platform specific. Native compilers never list their host - it is always implied. Generally, they are metapackages, pointing at a package that does specify the host. These in turn may be metapackages, pointing at a package where the host is the same as the target (both being the native architecture). ttarget_platforms {}_compilert_versionRRRN( RR4RaRtsubdirRRpRR)(RRYRmRRRtlanguage_compiler_key((s8lib/python2.7/site-packages/conda_build/jinja_context.pyR_s   c C`sd}|jp|j}|dks0|dkr?d}|}n|dkrQdnd}|jr|jjd|}|jjd |}nd |kr|jd d }|jd d }|d |d |d d j|}n|d |d |}|S(s Support configuration of Core Dependency Trees. We should define CDTs in a single location. The current idea is to emit parts of the following to index.json (the bits that the solver could make use of) and parts to about.json (the other bits). "system": { "os": { "type": "windows", "linux", "bsd", "darwin", "os_distribution": "CentOS", "FreeBSD", "Windows", "osx", "os_version": "6.9", "10.12.3", "os_kernel_version" : "2.6.32", "os_libc_family": "glibc", "os_libc_version": "2.12", } "cpu": { # Whichever cpu_architecture/cpu_isa we build-out for: # .. armv6 is compatible with and uses all CPU features of a Raspberry PI 1 # .. armv7a is compatible with and uses all CPU features of a Raspberry PI 2 # .. aarch64 is compatible with and uses all CPU features of a Raspberry PI 3 "cpu_architecture": "x86", "x86_64", "armv6", "armv7a", "aarch32", "aarch64", "powerpc", "powerpc64", "s390", "s390x", "cpu_isa": "nocona", "armv8.1-a", "armv8.3-a", # "?" because the vfpu is specified by cpu_architecture + cpu_isa + rules. "vfpu": "?", "cpu_endianness": "BE", "LE", } "gpu ?": { } "compilerflags": { # When put into a CDT these should be the base defaults. # Package builds can and will change these frequently. "CPPFLAGS": "-D_FORTIFY_SOURCE=2", "CFLAGS": "-march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -O2 -pipe", "CXXFLAGS": "-fvisibility-inlines-hidden -std=c++17 -fmessage-length=0 -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -O2 -pipe", "LDFLAGS": "-Wl,-O1,--sort-common,--as-needed,-z,relro", "FFLAGS": "-fopenmp", # These are appended to the non-DEBUG values: "DEBUG_CFLAGS": "-Og -g -Wall -Wextra -fcheck=all -fbacktrace -fimplicit-none -fvar-tracking-assignments", "DEBUG_CXXFLAGS": "-Og -g -Wall -Wextra -fcheck=all -fbacktrace -fimplicit-none -fvar-tracking-assignments", "DEBUG_FFLAGS": "-Og -g -Wall -Wextra -fcheck=all -fbacktrace -fimplicit-none -fvar-tracking-assignments", } } tcos6tppc64letaarch64tcos7t64tx86_64ti686tcdt_nametcdt_archRiiR(t host_archtarchRaRRRp( RRYRmRRRRt ver_buildtresult((s8lib/python2.7/site-packages/conda_build/jinja_context.pytcdt}s/   *cC`sW|dkrtdng}| rS| rSt|||jj\}}}n|S(sEReturns the final list of packages that are listed in host or build. This include all packages (including the indirect dependencies) that will be installed in the host or build environment. An example usage of this jinja function can be:: requirements: host: - curl 7.55.1 run_constrained: {% for package in resolved_packages('host') %} - {{ package }} {% endfor %} which will render to:: requirements: host: - ca-certificates 2017.08.26 h1d4fec5_0 - curl 7.55.1 h78862de_4 - libgcc-ng 7.2.0 h7cc24e2_2 - libssh2 1.8.0 h9cfc8f7_4 - openssl 1.0.2n hb7f436b_0 - zlib 1.2.11 ha838bed_2 run_constrained: - ca-certificates 2017.08.26 h1d4fec5_0 - curl 7.55.1 h78862de_4 - libgcc-ng 7.2.0 h7cc24e2_2 - libssh2 1.8.0 h9cfc8f7_4 - openssl 1.0.2n hb7f436b_0 - zlib 1.2.11 ha838bed_2 RRs/Only host and build dependencies are supported.(RR(RR RYRa(RRiRmRt package_namesR((s8lib/python2.7/site-packages/conda_build/jinja_context.pytresolved_packagess ! $c C`swtd|dtd|dtd|}ttj} | jtd|d||jdttd|d|d|d tt d|d|d|d t d tt d |d|d|d t tj j|jddtt|d|d|dtt|d|d|d|dttd |d|dttd |d|dtt|d|d|dtdtd| |S(s Return a dictionary to use as context for jinja templates. initial_metadata: Augment the context with values from this MetaData object. Used to bootstrap metadata contents via multiple parsing passes. Rtfor_envRtescape_backslashRaR{RkRmRRRRYt installeds conda-metaRRRRRRRttimetdatetimetenviron(RsR)RtdictRnRtupdateRR{RRRRRoRpt host_prefixRRRRRRR( tinitial_metadataRkRYRmRRRRatctxR((s8lib/python2.7/site-packages/conda_build/jinja_context.pytcontext_processors:           (7t __future__RRRt functoolsRRyRnRRRRtconda_interfaceRRRRstutilsRRRR R trenderR R R RRtvariantsRR7RR!RRRt BaseLoaderRVR)R4RR{RRRRRRRRRRRR(((s8lib/python2.7/site-packages/conda_build/jinja_context.pytsL      ("<  ,   % : &  !   B .