CC: | kmx [...] atlas.cz |
Subject: | Prima, PDL and MS Windows difficulties |
Hi Dmitry,
On Windows, with recent Prima (including 1.43) Prima::Config's %Prima::Config::Config is being populated with a lot of entries relating to the build directory - eg, for me:
'inc' => '-IC:/sisyphusion/Prima-1.43\\include -IC:/sisyphusion/Prima-1.43\\include\\generic',
'dlname' => 'C:\\sisyphusion\\Prima-1.43\\blib\\arch\\auto\\Prima\\Prima.dll',
'gencls' => 'C:\\sisyphusion\\Prima-1.43\\blib\\script\\gencls.bat',
'tmlink' => 'C:\\sisyphusion\\Prima-1.43\\blib\\script\\tmlink.bat',
'libname' => 'C:\\sisyphusion\\Prima-1.43\\blib\\arch\\auto\\Prima\\libPrima.a',
'incpaths' => [
'C:/sisyphusion/Prima-1.43\\include',
'C:/sisyphusion/Prima-1.43\\include\\generic'
],
'libs' => 'C:\\sisyphusion\\Prima-1.43\\blib\\arch\\auto\\Prima\\libPrima.a',
The problem is that PDL::Drawing::Prima (which is a prereq for PDL::Graphics::Prima) picks up those locations from Prima::Config and assumes that they still exist and still contain the files they once did.
Neither of those assumptions is inevitably correct.
We're thinking that Prima::Config should be specifying "instalment" locations rather than "build" locations.
But, if our thinking is wrong, then clearly the bug is instead in PDL::Drawing::Prima.
See
http://sourceforge.net/p/pdl/mailman/pdl-devel/thread/0FF8D75172AD4F9D9373859854236E65%40OwnerPC311012/#msg34193012
for the discussion we had.
Cheers,
Rob