Re: [Plib-users] PLIB for WIN32 - configure error C compiler cannot create executables

[John F. F. <joh...@cy...>]

Giovi,

     The first question is whether you are using MSVC 6.0 or some other 
version.  Later versions of Visual Studio (2008 and 2010) use something 
called "solution" files rather than "workspace" files.  The workspace 
and project files are specific to MSVC 6.0.  There may be a conversion 
utility if you have a later version.

     When I downloaded the SVN version of PLIB, I was able to start MSVC 
6.0 (professional version), open the workspace file, and build PLIB 
right away.  It may be a question of choice of words, but I didn't 
"rebuild 'plib.dsw'"; I used "plib.dsw" to build PLIB.

     Something doesn't look quite right, though:  PLIB itself doesn't 
refer to "plib/pw.h".  On the other hand, the examples do refer to 
"plib/ul.h" and files like that.  If you are building from the SVN 
version of PLIB, then you need to make a new directory named "plib" at 
the same level as the "trunk" directory and copy all the "*.h" files 
from the "trunk" directory into the new "plib" directory.  The include 
path was written for the release versions of the code, in which the 
"trunk" directory is in fact named "plib".

     Let me know if this fixes things.

         - John


On 11/3/2011 3:20 AM, Giovi wrote:
> Hello John,
> thanks a lot for your help!
> Maybe I have misunderstood the file "readme" of PLIB configuration.
>
> I have tried to use Visual C++ following the instructions:
>
> /Microsoft Visual C++:
> ~~~~~~~~~~~~~~~~~~~~~
> All you need to do is open the workspace "plib.dsw" in MSVC++,
> select the "plib" project (using Set Active Project in the Project
> menu), and build it (using "Rebuild All" in the Build menu).
>
> In the examples folder, open the workspace "plib_examples.dsw".
> Each example has a seperate project in the workspace. Select
> the one you want and build it. Then you should be able to hit
> the Go icon on the toolbar and try it out.
>
> For your own application, please note that the plib workspace
> leaves all the necessary includes (*.h) and libraries (*.lib)
> in the plib root directory (same as workspace). The debug
> libraries are given a '_d' suffix. Where ever you put those
> files, make sure #include <plib/ul.h> works so your code is
> more portable.
> /
>
> But when I rebuild "plib.dsw" I get the error:
> Impossible top open plib/pw.h file: no such file or directory
>
> I get same error for all plib files.
>
> What Am I doing wrong?
>
> Many thanks in advance for your help!
>
> Thanks and regards
>
>
>
> 2011/11/1 John F. Fay <joh...@cy... 
> <mailto:joh...@cy...>>
>
>     Giovi,
>
>         Hello and welcome to the PLIB community.
>
>         I'm a little confused about what you are trying to do.  If
>     you're trying to build PLIB for Windows to link to C++ programs in
>     Windows with a development environment such as Microsoft Visual
>     C++ or ".Net", then you should not be using Cygwin.  On the other
>     hand, if you're trying to build for Cygwin (which runs in Windows
>     but feels a lot like Linux), then you need Cygwin.
>
>         Unfortunately the "config.log" file didn't make it to my
>     e-mail.  Can you repeat the last few lines of it here?
>
>             - John
>