Re: [Plplot-devel] Anyone tried out ldc for D?

On 2010-07-16 14:29-0600 Orion Poplawski wrote:
> Fedora now has the ldc compiler, but it appears that plplot is hardcoded for
> dmd? I tried:
>
> cmake -DENABLE_d=ON -DCMAKE_D_COMPILER=ldc ..
>
> But still get:
>
> -- D Compiler Install Prefix (use D_PATH env var to override): CMAKE_D_COMPILER-
> CMake Error: your D compiler: "CMAKE_D_COMPILER-NOTFOUND" was not found.
> Please set CMAKE_D_COMPILER to a valid compiler path or name.
> -- Configuring incomplete, errors occurred!
> -- WARNING: no working D compiler so disabling D bindings and examples.
What happens if you use the environment variable approach? i.e.,
export DC=ldc
in an initially empty build tree before cmake is executed. The
environment approach was the one that was historically recommended
when I first started using cmake, and it continues to be the approach
I use for C (CC), C++ (CXX), and Fortran (FC) to specify the compiler
(and optionally flags for that compiler). The only mention in
the cmake documentation I can find for CMAKE_C_COMPILER is in the
cross-compilation documentation. I have never used that to specify the
C compiler in a normal build environment, and I am not sure it is (or the
corresponding CMAKE_D_COMPILER is) meant to be used in a normal build
environment.
Alan
__________________________
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________
Linux-powered Science
__________________________

On 2010-07-16 14:29-0600 Orion Poplawski wrote:
> Fedora now has the ldc compiler, but it appears that plplot is hardcoded for
> dmd? I tried:
>
> cmake -DENABLE_d=ON -DCMAKE_D_COMPILER=ldc ..
>
> But still get:
>
> -- D Compiler Install Prefix (use D_PATH env var to override): CMAKE_D_COMPILER-
> CMake Error: your D compiler: "CMAKE_D_COMPILER-NOTFOUND" was not found.
> Please set CMAKE_D_COMPILER to a valid compiler path or name.
> -- Configuring incomplete, errors occurred!
> -- WARNING: no working D compiler so disabling D bindings and examples.
What happens if you use the environment variable approach? i.e.,
export DC=ldc
in an initially empty build tree before cmake is executed. The
environment approach was the one that was historically recommended
when I first started using cmake, and it continues to be the approach
I use for C (CC), C++ (CXX), and Fortran (FC) to specify the compiler
(and optionally flags for that compiler). The only mention in
the cmake documentation I can find for CMAKE_C_COMPILER is in the
cross-compilation documentation. I have never used that to specify the
C compiler in a normal build environment, and I am not sure it is (or the
corresponding CMAKE_D_COMPILER is) meant to be used in a normal build
environment.
Alan
__________________________
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________
Linux-powered Science
__________________________