Compiling with Visual Studio 2008 « pnotepad.org forums

Compiling with Visual Studio 2008

(18 posts) (3 voices)

Started 3 years ago by kuukkeli
Latest reply from kuukkeli

Tags:

kuukkeli
Member

I've decided to learn some C/C++ (I know the very basics but as Python has always been enough for my own projects I've been stuck with those rudimentary skills for years). As PN is both interesting and rather small project I'm trying to use it as some sort of a learning environment. I just need couple of answers first:

1. Installing Boost has far too many options to my taste (I'm using the Windows installer provided by 'boostpro computing'). Which of the compiled library variants are needed to compile PN? Which of them I should install?

2. Besides linking WTL and Boost is there anything special to do before trying to compile PN?

3. PN sources have some Visual Studio project files which are (if I'm correct) for older version than 2008. Does using VS2008 cause any issues because of that?

And please, don't expect much contributions from me in a long time - I'm sure I'll be challenged enough by merely getting the current sources compiled :)

Posted 3 years ago #
simon
PN Developer

1. I normally just download the boost source and unzip it, you shouldn't need to build any part of boost for working with PN normally. The only reason to build anything would be if you wanted to update the version of boost::python that PyPN is using.

The bits of boost used in the main application are all header-only meaning they don't need compiling before PN can use them.

2. Currently there are a few extra steps as we're using a custom build of Scintilla with some patches. You need to place the source for scintilla (http://scintilla.org) in the include\scintilla directory, and then place the files from this zip on top:

http://pnotepad.org/files/altregex_ns.zip

3. I think VS2008 should be fine to just convert the project files, but I haven't tried recently. Post any errors you get and I'll try to help.

Enjoy!

Posted 3 years ago #

kuukkeli
Member

After some effort this is where I'm stuck. I had to copy a new version of boost::python to /lib because after converting the project it looked for vc-90 version and I just couldn't figure out how to change that, but I suppose this has nothing to do with it.

Compiling...
stdafx.cpp
e:\tomi\ohjelmointi\pn2\include\taskdialog.h(453) : error C2504: 'CDialogBaseUnits' : base class undefined
        e:\tomi\ohjelmointi\pn2\include\taskdialog.h(1978) : see reference to class template instantiation 'CTask98DialogImpl' being compiled
        with
        [
            T=CTask98Dialog
        ]
e:\tomi\ohjelmointi\pn2\dockingframework\extdockingwindow.h(344) : error C2664: 'GetThemeSysFont' : cannot convert parameter 3 from 'LOGFONT *' to 'LOGFONTW *'
        Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast
Creating browse information file...
Microsoft Browse Information Maintenance Utility Version 9.00.21022
Copyright (C) Microsoft Corporation. All rights reserved.
BSCMAKE: error BK1506 : cannot open file '.\Debug\appsettings.sbr': No such file or directory

That's the only error I'm getting now but I have no idea what it's about.

Posted 3 years ago #

kuukkeli
Member

After updating WTL through SVN I got rid of one error but this I can't solve:

6>e:\tomi\ohjelmointi\pn2\dockingframework\extdockingwindow.h(344) : error C2664: 'GetThemeSysFont' : cannot convert parameter 3 from 'LOGFONT *' to 'LOGFONTW *'
6>        Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast
6>Creating browse information file...
6>Microsoft Browse Information Maintenance Utility Version 9.00.21022
6>Copyright (C) Microsoft Corporation. All rights reserved.
6>BSCMAKE: error BK1506 : cannot open file '.\Debug\appsettings.sbr': No such file or directory
6>Build log was saved at "file://e:\Tomi\Ohjelmointi\PN2\Debug\BuildLog.htm"
6>pn - 2 error(s), 0 warning(s)

Posted 3 years ago #

simon
PN Developer

Hi, please update to the latest WTL from their subversion (sorry!) as this should fix the CDialogBaseUnits bit. As for the GetThemeSysFont thing I think you can just change it to LOGFONTW and it should work. Let me know, and I'll try and see if there's some pattern - it's different in different versions of the Platform SDK.

Posted 3 years ago #
kuukkeli
Member

simon:
"As for the GetThemeSysFont thing I think you can just change it to LOGFONTW and it should work."

Could you be a bit more precise? I looked at the file that gives the error but I have no idea what you mean (I guess that's a symptom of being C++ newbie).

Couple more questions too.

1. I've been building and checking the error messages to see which projects need which additional includes. Is there easier (and more refined) way to do it?

2. As I mentioned earlier I couldn't get PyPN to compile without copying vc90 version of required boost library. Is there a way to keep vc80 version after the project conversion?

3. For PN projects that require ATL should I use static or dynamic linking?

Posted 3 years ago #
simon
PN Developer
GetThemeSysFont:

The bit of code we're looking at is this:
```
LOGFONTW lf;
// Newer SDKs fix this define:
#ifdef NTDDI_WIN6SP1
    ::GetThemeSysFont(m_winTheme, TMT_SMALLCAPTIONFONT, &lf);
#else
    ::GetThemeSysFont(m_winTheme, TMT_SMALLCAPTIONFONT, (LOGFONT *)&lf);
#endif
```
The bit in the #else section is the code giving you trouble, and it's there because older versions of the platform SDK incorrectly defined the GetThemeSysFont method as taking LOGFONT instead of LOGFONTW which is what they really wanted (so LOGFONTW is cast to LOGFONT).

I suspect that instead of NTDDI_WIN6SP1 we want something earlier, perhaps you could see if NTDDI_WIN6 works for you? If so, let me know and I'll change it in the code for good.

Answers to your other questions:

1. Unfortunately there's no easy way to tell which prerequisites you are missing, it does get easier with experience to guess ;)

2. I think the way boost works you'll have to stick with the vc90 version for your build of PyPN. Is this a problem?

3. I generally select "Not using ATL" and haven't found this to be a problem - this is only relevant when using the non-template parts of ATL anyway which we're not doing at the moment. If you do have to use it, go for dynamic linking but note we'll need to add extra files to the installer if we ship that change.
Posted 3 years ago #
jumpfroggy
Member

I'd love to capture this on a wiki page, so others can find a step-by-step to compile PN. I know it'd help me a lot (I've spent about 5-8 hours so far, still can't get it to compile).

Can we fix the wiki so we can get this information in there? Thanks!

Posted 3 years ago #
simon
PN Developer

jumpfroggy has put an excellent summary of the current build steps here:

http://pnotepad.org/docs/dev/how_to_compile_pn

Note that as of a couple of days ago, you should be able to get the current scintilla source (it's not been released as an official package yet) and use that without the patches. I'll confirm when I've tried it. This should simplify things.

Another thing to note is that I put boost and WTL in my directories configuration in Visual Studio meaning that I don't need to modify the project files. This saves the project files from having library paths specific to me in them. The method in the wiki will work fine, though.

Posted 3 years ago #
kuukkeli
Member
Finally I had time to return to this compile attempt. I got the PN to compile but I'll return to remaining problems a bit later. Now I'd need to know if any of the things I did are somehow wrong.

First, to fix the GetThemeSysFont I ended up commenting out the whole if-else part and left only ::GetThemeSysFont(m_winTheme, TMT_SMALLCAPTIONFONT, &lf); in its place. Just changing NTDDI_WIN6SP1 to NTDDI_WIN6 didn't make any difference.

Second, in addition to changes mentioned in 'how to' above I had to include boost in two other projects as well (ctagsnavigator, pypn). For pypn I also had to replace the Python related include with full path to \Python25\include library as it didn't find it otherwise and add vc90 boost files to \lib\boost-python-2.5. And finally I had to change atlres.h in pn.rc to full path to that file.

With the above changes PN compiles and works. Project tests still gives errors though because of the following:
```
#include "../pnwtl/allocator.h"
#include "../pnwtl/string.h"
```
These two files don't exist. I can fix the first by dropping pnwtl from the path but there's no obvious fix to second.

My main concern though is the fact that while pypn compiles without errors or warnings it doesn't work. PN doesn't find it at all. I made config.xml for it and it finds ctags correctly but pypn doesn't show up. I copied the pypn and scripts folders from svn to PN's home directory but it made no difference. I have no idea how to make pypn work.
Posted 3 years ago #
simon
PN Developer
Thanks, I fixed the allocator and string thing, they should have been:
```
#include "../allocator.h"
#include "../pnextstring.h"
```
The string file was renamed recently to fix clashes with the standard library.

As for PyPN, you could step into the extension loading to find out why it doesn't work. When you say the PN home directory, I presume you mean inside bin? PyPN needs your bin folder to look like:
```
bin
 |- pypn
 |   |- decorators.py
 |- scripts
 |- schemes
 |- taggers
```
In terms of the include directories, I personally think it's easier to just add Boost and WTL to your global include directories (Tools|Options|Projects and Solutions|VC++ Directories) which then makes these things available to all projects where needed. YMMV.

I'll have to look more into the GetThemeSysFont thing. Is NTDDI_WIN6 even defined in your environment?
Posted 3 years ago #
kuukkeli
Member
First, two more fixes. In file actests.cpp there are two more imports with extra pnwtl:
```
#include "../pnwtl/autocomplete.h"
#include "../pnwtl/pnstrings.h"
```
Then about PyPN. I don't (again) fully grasp the meaning of your advice. How do I "step into" extension loading? Is there a log somewhere or what? And yes, with PN home directory I was referring to bin.

Thanks for all the help this far.
Posted 3 years ago #
simon
PN Developer

Thanks, done.

For PyPN, as you have built PN you can put a breakpoint in App::LoadExtensions() and then run the program in the debugger. You'll then be able to walk step by step through the extensions being loaded and find out at what point PN fails to load PyPN.

Posted 3 years ago #

kuukkeli
Member

Assuming I did it correctly this is the debugger output concerning PyPN:

'pn.exe': Loaded 'E:\Tomi\Ohjelmointi\pnwtl\bin\pypn.dll', Symbols loaded.
'pn.exe': Loaded 'E:\Tomi\Ohjelmointi\pnwtl\bin\boost_python-vc80-mt-gd-1_35.dll'
LDR: LdrpWalkImportDescriptor() failed to probe e:\Tomi\Ohjelmointi\pnwtl\bin\boost_python-vc80-mt-gd-1_35.dll for its manifest, ntstatus 0xc0150002
'pn.exe': Unloaded 'E:\Tomi\Ohjelmointi\pnwtl\bin\pypn.dll'
'pn.exe': Unloaded 'E:\Tomi\Ohjelmointi\pnwtl\bin\boost_python-vc80-mt-gd-1_35.dll'
Failed to load extension: pypn.dll'pn.exe'

Does it ring any bells for you (I'm, as expected, drawing a blank)?

Posted 3 years ago #

simon
PN Developer
Ah, this is because the vc80-mt-gd-1_35.dll version of boost python is built against the Visual Studio 2005 debug libraries, these are not on your machine because you only have VS 2008. You have a few options:
1. Build boost python for vc90 and use that
2. Download a copy of the 2005 DebugCRT and install it, that should work ok but no guarantees
3. Just use a release build of pypn, hopefully all the dlls you need should be on the machine already and if not they're in the prerequisites folder under the installer.
Posted 3 years ago #
kuukkeli
Member

Concerning option 1:

I already have boost_python-vc90-mt-gd-1_35.dll and boost_python-vc90-mt-gd-1_35.lib in lib\boost-python-2.5 folder because I can't compile PN without vc90 version. To me that would seem to fulfil option 1 but obviously it doesn't. What additional steps am I missing from option 1?

Also (possibly related) why does boost_python-vc80-mt-gd-1_35.dll still end up in the bin directory while compiling requires vc90 version (if I replace it with vc90 version I get an error than vc80 version isn't found)?

Posted 3 years ago #
simon
PN Developer

Ah, lightbulb moment! The project is set to link to that DLL by the inclusion of boost_python-vc80-mt-gd-1_35.lib in the linker inputs in the project settings. Change that to the relevant lib built for vc90 and then everything should start working. The vc80 dll is copied by the post build step, also configured in the project settings.

Posted 3 years ago #

kuukkeli
Member

Like you said, everything SHOULD have worked :) Instead though I got a bunch of unresolved externals. Here's the whole error set from PyPN after the above changes:

1>mod_pn.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall boost::python::objects::enum_base::~enum_base(void)" (__imp_??1enum_base@objects@python@boost@@QAE@XZ) referenced in function "public: __thiscall boost::python::enum_<enum FindNextResult>::~enum_<enum FindNextResult>(void)" (??1?$enum_@W4FindNextResult@@@python@boost@@QAE@XZ)
1>mod_pn.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall boost::python::objects::class_base::~class_base(void)" (__imp_??1class_base@objects@python@boost@@QAE@XZ) referenced in function "public: __thiscall boost::python::class_<class extensions::IDocument,class boost::noncopyable_::noncopyable,struct boost::python::detail::not_specified,struct boost::python::detail::not_specified>::~class_<class extensions::IDocument,class boost::noncopyable_::noncopyable,struct boost::python::detail::not_specified,struct boost::python::detail::not_specified>(void)" (??1?$class_@VIDocument@extensions@@Vnoncopyable@noncopyable_@boost@@Unot_specified@detail@python@5@U6785@@python@boost@@QAE@XZ)
1>mod_scintilla.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: __thiscall boost::python::objects::class_base::~class_base(void)" (__imp_??1class_base@objects@python@boost@@QAE@XZ)
1>mod_pn.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) protected: __thiscall boost::python::objects::enum_base::enum_base(char const *,struct _object * (__cdecl*)(void const *),void * (__cdecl*)(struct _object *),void (__cdecl*)(struct _object *,struct boost::python::converter::rvalue_from_python_stage1_data *),struct boost::python::type_info,char const *)" (__imp_??0enum_base@objects@python@boost@@IAE@PBDP6APAU_object@@PBX@ZP6APAXPAU4@@ZP6AX3PAUrvalue_from_python_stage1_data@converter@23@@ZUtype_info@23@0@Z) referenced in function "public: __thiscall boost::python::enum_<enum FindNextResult>::enum_<enum FindNextResult>(char const *,char const *)" (??0?$enum_@W4FindNextResult@@@python@boost@@QAE@PBD0@Z)
1>mod_pn.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) protected: void __thiscall boost::python::objects::enum_base::add_value(char const *,long)" (__imp_?add_value@enum_base@objects@python@boost@@IAEXPBDJ@Z) referenced in function "public: struct boost::python::enum_<enum FindNextResult> & __thiscall boost::python::enum_<enum FindNextResult>::value(char const *,enum FindNextResult)" (?value@?$enum_@W4FindNextResult@@@python@boost@@QAEAAU123@PBDW4FindNextResult@@@Z)
1>mod_pn.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) protected: static struct _object * __cdecl boost::python::objects::enum_base::to_python(struct _typeobject *,long)" (__imp_?to_python@enum_base@objects@python@boost@@KAPAU_object@@PAU_typeobject@@J@Z) referenced in function "private: static struct _object * __cdecl boost::python::enum_<enum FindNextResult>::to_python(void const *)" (?to_python@?$enum_@W4FindNextResult@@@python@boost@@CAPAU_object@@PBX@Z)
1>mod_pn.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall boost::python::converter::shared_ptr_deleter::shared_ptr_deleter(struct boost::python::converter::shared_ptr_deleter const &)" (__imp_??0shared_ptr_deleter@converter@python@boost@@QAE@ABU0123@@Z) referenced in function "private: static void __cdecl boost::python::converter::shared_ptr_from_python<class extensions::IDocument>::construct(struct _object *,struct boost::python::converter::rvalue_from_python_stage1_data *)" (?construct@?$shared_ptr_from_python@VIDocument@extensions@@@converter@python@boost@@CAXPAU_object@@PAUrvalue_from_python_stage1_data@234@@Z)
1>mod_scintilla.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: __thiscall boost::python::converter::shared_ptr_deleter::shared_ptr_deleter(struct boost::python::converter::shared_ptr_deleter const &)" (__imp_??0shared_ptr_deleter@converter@python@boost@@QAE@ABU0123@@Z)
1>mod_pn.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) void __cdecl boost::python::objects::register_dynamic_id_aux(struct boost::python::type_info,struct std::pair<void *,struct boost::python::type_info> (__cdecl*)(void *))" (__imp_?register_dynamic_id_aux@objects@python@boost@@YAXUtype_info@23@P6A?AU?$pair@PAXUtype_info@python@boost@@@std@@PAX@Z@Z) referenced in function "void __cdecl boost::python::objects::register_dynamic_id<class extensions::IDocument>(class extensions::IDocument *)" (??$register_dynamic_id@VIDocument@extensions@@@objects@python@boost@@YAXPAVIDocument@extensions@@@Z)
1>mod_scintilla.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) void __cdecl boost::python::objects::register_dynamic_id_aux(struct boost::python::type_info,struct std::pair<void *,struct boost::python::type_info> (__cdecl*)(void *))" (__imp_?register_dynamic_id_aux@objects@python@boost@@YAXUtype_info@23@P6A?AU?$pair@PAXUtype_info@python@boost@@@std@@PAX@Z@Z)
1>mod_pn.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) void * __cdecl boost::python::objects::find_dynamic_type(void *,struct boost::python::type_info,struct boost::python::type_info)" (__imp_?find_dynamic_type@objects@python@boost@@YAPAXPAXUtype_info@23@1@Z) referenced in function "private: virtual void * __thiscall boost::python::objects::pointer_holder<class boost::shared_ptr<class extensions::IDocument>,class extensions::IDocument>::holds(struct boost::python::type_info,bool)" (?holds@?$pointer_holder@V?$shared_ptr@VIDocument@extensions@@@boost@@VIDocument@extensions@@@objects@python@boost@@EAEPAXUtype_info@34@_N@Z)
1>mod_scintilla.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) void * __cdecl boost::python::objects::find_static_type(void *,struct boost::python::type_info,struct boost::python::type_info)" (__imp_?find_static_type@objects@python@boost@@YAPAXPAXUtype_info@23@1@Z) referenced in function "private: virtual void * __thiscall boost::python::objects::value_holder<class PNScintilla>::holds(struct boost::python::type_info,bool)" (?holds@?$value_holder@VPNScintilla@@@objects@python@boost@@EAEPAXUtype_info@34@_N@Z)
1>..\bin/pypn.dll : fatal error LNK1120: 9 unresolved externals

Posted 3 years ago #

RSS feed for this topic

Reply

You must log in to post.