Your IP : 216.73.216.213
��Yf8 � @ s� d Z d d l Z d d l Z y d d l Z Wn e k
rH d Z Yn XGd d � d � Z d d � Z d d � Z d d
� Z d d � Z d
Z
d Z d Z d Z
d S)a� Extension management for Windows.
Under Windows it is unlikely the .obj files are of use, as special compiler options
are needed (primarily to toggle the behavior of "public" symbols.
I don't consider it worth parsing the MSVC makefiles for compiler options. Even if
we get it just right, a specific freeze application may have specific compiler
options anyway (eg, to enable or disable specific functionality)
So my basic strategy is:
* Have some Windows INI files which "describe" one or more extension modules.
(Freeze comes with a default one for all known modules - but you can specify
your own).
* This description can include:
- The MSVC .dsp file for the extension. The .c source file names
are extracted from there.
- Specific compiler/linker options
- Flag to indicate if Unicode compilation is expected.
At the moment the name and location of this INI file is hardcoded,
but an obvious enhancement would be to provide command line options.
� Nc @ s^ e Z d Z d Z d d � Z d d � Z d d � Z d d � Z d
d � Z d d
� Z d S)�
CExtensionz8An abstraction of an extension implemented in C/C++
c C s( | | _ | | _ g | _ g | _ d S)N)�name�sourceFiles�compilerOptions�
linkerLibs)�selfr r � r �G/opt/alt/python35/lib64/python3.5/Tools/freeze/checkextensions_win32.py�__init__"