Hi John,

> zconf.h is taken care off,

Ok, that is good, but could you please 
shared what you did. I think you mentioned 
finding something about editing zconf.h...

Found what, where... what edits did you do?

This is to just HELP the NEXT person that 
stumbles over this...

And may even get one of the 'maintainer' to 
put a more permanent 'fix' online so there is 
no next time ;=))

> pui vs. pu

In MY 3rdparty\lib directory they are -
pu.lib and pu_d.lib, and
puaux.lib and puaux_d.lib
for Release and Debug respectively...

In unix/linux they are libplibpu.a and 
libplibpuaux.a...

But I guess pui.lib is also possible...

> puaux vs.puAux,  is that significant?

I hope you know normally the windows system 
does NOT care about CaSe ;=)) so these are the 
same...

> there is no pu.lib or puaux.lib.

Rubbish! But as you sort of point out, that 
could be pui.lib and puiaux.lib in your 
environment...

If msvc can not find a library then it will 
say that!

It didn't, so it found somethings, but it just 
missing a function link - puaList()... And when 
it misses one library function like this it 
will usually report a LONG list of 'missing'...

As to finding it/them have you tried in -
 3rdparty\lib > dir pu*.lib /s

If not, even > dir c:\pu*.lib /s ;=)) will take 
a little longer, but will get you there... unless 
it is on another logical drive...

> wasn't able to track down the log file, 
> where would you find it...

Again, in the 'build' directory you have 
chosen in CMake do -
 > dir *.log /s
should get you there...

In my case, my build directory is -
C:\FG\10\flightgear\build
and it is found in -
 ...build\src\Main\fgfs.dir\Debug
and
 ...build\src\Main\fgfs.dir\Release

You need to find it so you can CHECK exactly 
what plib libraries msvc link.exe is using 
when building fgfs.exe...

Also, as a suggestion, I would not bother yet 
about building the Debug configuration, and 
concentrate on building the Release 
configuration...

Now when you get the pu*.lib story straight,
you can manually modify CMakeCache.txt 
before loading the CMAke GUI, or fix them 
directly in the GUI... [configure] then 
[generate], then back into msvc...

HTH.

Regards,
Geoff.



------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to