pnotepad.org forums » Tag: build

pnotepad.org forums » Tag: build - Recent Posts http://pnotepad.org/forums/tags/build Programmer's Notepad Forums en-US Thu, 09 Feb 2012 07:12:10 +0000 http://bbpress.org/?v=1.0.3 <![CDATA[Search]]> q http://pnotepad.org/forums/search.php About how to compile PN (simon) http://pnotepad.org/forums/topic/5197#post-7908 Mon, 16 May 2011 17:55:19 +0000 simon 7908@http://pnotepad.org/forums/ The "d" stands for "debug" - it's the debug version of the runtime libraries. If you build the Release build you'll only need the ones that PN includes. Nice to hear about it working on OSX, thanks! About how to compile PN (CoDEmanX) http://pnotepad.org/forums/topic/5197#post-7907 Mon, 16 May 2011 16:49:08 +0000 CoDEmanX 7907@http://pnotepad.org/forums/ Ok thanks. I copied the config.xml from portable-pn rc1 and also the msvcr100.dll and msvcp100.dll. When i launched pn.exe, it gave me error: msvcr100d.dll / msvcp100d.dll not found. Renaming the dlls without d at the end gives another error (entry point not found...), so I downloaded the needed DLLs from dll-files.com and it's now working. I guess the d stands for deutsch (german), 'cause i built PN on german Windows 7?! With portable settings and the DLLs, it works on Mac OSX using Crossover (Wine core) too. About how to compile PN (simon) http://pnotepad.org/forums/topic/5197#post-7906 Mon, 16 May 2011 08:16:48 +0000 simon 7906@http://pnotepad.org/forums/ This is done with a flag in config.xml. If you look under the <code>installer\configs\</code> directory you'll find the config.xml to drop in for portable mode. Put that in the same directory as pn.exe and you're running "portable" - the build itself is identical. About how to compile PN (CoDEmanX) http://pnotepad.org/forums/topic/5197#post-7892 Thu, 12 May 2011 18:45:00 +0000 CoDEmanX 7892@http://pnotepad.org/forums/ I built all projects of the solution, SciLexer.dll was created in that process and everything is working perfectly. Got another question: how to switch build type between portable and installation distribution? About how to compile PN (CoDEmanX) http://pnotepad.org/forums/topic/5197#post-7818 Mon, 04 Apr 2011 18:03:25 +0000 CoDEmanX 7818@http://pnotepad.org/forums/ I'll check for the SciLexer.dll, thanks Simon! Code for description attribute attached: <a href="http://code.google.com/p/pnotepad/issues/detail?id=609#c5" rel="nofollow">http://code.google.com/p/pnotepad/issues/detail?id=609#c5</a> BTW: i see many appearences of func="yes" in the API files but there is no code for it. Can we drop it and add the APIs to our repo for later improvement? About the How to compile tutorial (needs another update): Microsoft deprecated the Visual C++ include directories. Now it's necessary to add boost and wtl to each project of the solution. VS2010 stores the information as property sheet along with the project files, therefore one has to change the already added paths (or place boost and wtl where Simon put them) About how to compile PN (simon) http://pnotepad.org/forums/topic/5197#post-7812 Mon, 04 Apr 2011 10:28:32 +0000 simon 7812@http://pnotepad.org/forums/ For change submission there are two options: 1. Create a fork on Google Code and push to that as you please, then ask me to pull the changes with a patch issue on Google Code. 2. Create a patch and attach it to a patch issue. About how to compile PN (simon) http://pnotepad.org/forums/topic/5197#post-7810 Mon, 04 Apr 2011 10:05:29 +0000 simon 7810@http://pnotepad.org/forums/ <code>CXX0030: Error: expression cannot be evaluated</code> This is an error from the watch window or the debugger at any rate, and shouldn't be related to the actual problem you're seeing. You'll definitely need the accelerator method because otherwise you'll have an invalid accelerator table which will cause all sorts of problems (as you're seeing). If the text view is not drawing, then the most likely problem is that the scintilla DLL has not built, or is not working properly. Can you check you have a SciLexer.dll in your bin directory? About how to compile PN (CoDEmanX) http://pnotepad.org/forums/topic/5197#post-7809 Sun, 03 Apr 2011 21:24:00 +0000 CoDEmanX 7809@http://pnotepad.org/forums/ I went back to revision f2a2b6461cb6 and converted it, but same errors: The call stack: <code> > pn.exe!CChildFrame::GetToolAccelerators() Line 2959 + 0x1b bytes C++ pn.exe!CMainFrame::OnChildNotify(unsigned int __formal, unsigned int wParam, long lParam, int & bHandled) Line 532 + 0x8 bytes C++ pn.exe!CMainFrame::ProcessWindowMessage(HWND__ * hWnd, unsigned int uMsg, unsigned int wParam, long lParam, long & lResult, unsigned long dwMsgMapID) Line 112 + 0x28 bytes C++ pn.exe!WTL::CMDIFrameWindowImpl<CMainFrame,WTL::CMDIWindow,dockwins::CDockingFrameTraitsT<dockwins::CSimpleSplitterBar<3>,114229248,262400> >::MDIFrameWindowProc(HWND__ * hWnd, unsigned int uMsg, unsigned int wParam, long lParam) Line 1499 + 0x27 bytes C++ __vfptr = CXX0030: Error: expression cannot be evaluated m_hAccel CXX0030: Error: expression cannot be evaluated m_hSubMenu = CXX0017: Error: symbol "" not found CSMenuT<1> = {m_hMenu=??? } m_hSubMenu = CXX0030: Error: expression cannot be evaluated m_Tools = [...] only contains bunch of (error) = 0 </code> If i skip the accel function and ignore the window check, PN shows up but the text view is broken (doesn't draw itself) About how to compile PN (CoDEmanX) http://pnotepad.org/forums/topic/5197#post-7808 Sun, 03 Apr 2011 17:59:54 +0000 CoDEmanX 7808@http://pnotepad.org/forums/ Ok, new problems. I moved to a new system, Windows 7 Starter and VS 2010 +SP1. Sources compile without errors, but when i run it, i get "cant evaluate" error here: HACCEL CChildFrame::GetToolAccelerators() { SchemeTools* pTools = ToolsManager::GetInstance()->GetToolsFor( GetTextView()->GetCurrentScheme()->GetName() ); return pTools->GetAcceleratorTable(); } I replaced the function body by return NULL; but it gave me new error in atlwin.h (Expression: ::isWindow(m_hWnd); I used the latest code from repo. Please help, Simon! About how to compile PN (CoDEmanX) http://pnotepad.org/forums/topic/5197#post-7806 Sat, 02 Apr 2011 00:09:22 +0000 CoDEmanX 7806@http://pnotepad.org/forums/ I got it working, now thinking about how extend the *.api files Either i add a "desc" attribute to KeyWord and Param tag* or introduce an ending Param tag and a Description block to put the text as character data into the XML apis (got that working as well, although it's ugly code...) *(not for Overload, because i don't think anyone will need it) Currently i tend to the former Simon, do i have to send you my code so you can merge it or can i push it to the repo somehow myself? About how to compile PN (CoDEmanX) http://pnotepad.org/forums/topic/5197#post-7773 Thu, 24 Mar 2011 13:04:24 +0000 CoDEmanX 7773@http://pnotepad.org/forums/ Okay, i performend <code>hg update -r f2a2b6461cb6</code> for VS 2008 compatible source code and it built without errors :) (Using Boost 1.42) My change to CallTip is experimental at the moment. I changed the background color for xp-like quickinfo look: <code>colourBG.desired = ColourDesired(0xff, 0xff, 0xe1);</code> And i tested the multi-line support, which already exists! <a href="http://pnotepad.googlecode.com/issues/attachment?aid=3212458882931685048&name=PNotepad_API_Tooltip_Multiline_Support.png&token=ab48ed7a7ada13b4521b187b7fe3c370&inline=1">Screenshot</a> Posted here: <a href="http://code.google.com/p/pnotepad/issues/detail?id=609&q=tooltip">PN @ Google Code</a> I'm only a hobby coder and not familiar with serious C++, so I don't know if I can get a calltip enhancement working; help always appreciated :) About how to compile PN (simon) http://pnotepad.org/forums/topic/5197#post-7760 Mon, 21 Mar 2011 13:51:23 +0000 simon 7760@http://pnotepad.org/forums/ Oh also, I think you now need Boost 1.45 and that explains a couple of other errors. About how to compile PN (simon) http://pnotepad.org/forums/topic/5197#post-7759 Mon, 21 Mar 2011 13:49:21 +0000 simon 7759@http://pnotepad.org/forums/ Also, what's your change to CallTip? If it's of general interest then please send as a patch for consideration! About how to compile PN (simon) http://pnotepad.org/forums/topic/5197#post-7758 Mon, 21 Mar 2011 13:48:52 +0000 simon 7758@http://pnotepad.org/forums/ Thanks, and sorry! 2010 is right, and as of that switch I don't think you should need to download a separate SDK - the included bits are up-to-date (equivalent to 7.0a I think). The errors in your trace look largely to be related to 2010's C++0x syntax features, you'll need to revert more files to get 2008 to work again. I'll update the docs. About how to compile PN (CoDEmanX) http://pnotepad.org/forums/topic/5197#post-7749 Fri, 18 Mar 2011 12:00:29 +0000 CoDEmanX 7749@http://pnotepad.org/forums/ Hey there, i wanted to compile PN with minimal changes in the CallTip.cxx and followed the tutorial instruction: <a href="http://pnotepad.org/docs/dev/how_to_compile_pn" rel="nofollow">http://pnotepad.org/docs/dev/how_to_compile_pn</a> So i downloaded the <a href="http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c17ba869-9671-4330-a63e-1fd44e0e2505&displaylang=en">latest Windows SDK</a> for Windows 7 and .NET 3.5. "Make sure to register the SDK with Visual Studio" --> error thrown: "Your system does not have Visual Studio 2005 or Visual Studio 2008 installed." I found a solution <a href="http://blogs.msdn.com/b/windowssdk/archive/2009/08/21/windows-sdk-configuration-tool-may-report-an-error-when-os-display-format-is-not-english.aspx">here</a>: At the Windows SDK command prompt, type "WindowsSdkVer.exe -version:v7.0" without quotes "Add the boost directory to your Visual C++ include directories" --> i added it to the include files category (for “Show directories for” i selected “Include Files”). This gave me least errors on build. May i have to add the libs directory to the library category as well? No problems with WTL, but i had to revert several PN source files to revision <code>f2a2b6461cb6</code> to make it work with VS 2008 (since rev <code>b69cc67a9020</code> VS 2010 is required) On build, i got more than <a href="http://nopaste.info/62b60a014d_nl.html">300 errors</a>. Any ideas how to solve these problems? @Simon: please update the tutorial 1) VS 2008 --> VS 2010 2) WinSDK 2008 (v6.0A / v6.1) --> WinSDK v7.0 3) more details on how to add boost in VS Thanks you very much! How to compile multiple files - one project (mohseni) http://pnotepad.org/forums/topic/322#post-7038 Mon, 07 Jun 2010 18:36:30 +0000 mohseni 7038@http://pnotepad.org/forums/ Dear Members, I'am trying to define a function(a simple function which make a led on/off) and add it to main source code by including a header but the main source couldn't determine/define the function. I recieve below error: ********* main.c12: undefined reference to 'ledon' ******** some told me I should compile and linke them together. how? Would you please tell me where is problem? %%%%%%%%% here is the codes %%%%%%%%% main: ------------------------ #include <avr/io.h> #include <util/delay.h> #include "ledon.h" int main() { DDRA=0xff; while(1) { ledon(); } } --------------------------- Function( it's a simple function which make a led on/off--------- void ledon() { PORTA |= 0x80; _delay_ms(100); PORTA &= ~0x80; _delay_ms(100); } ------------------------- header--------------------- #ifndef MYHEADER_H #define MYHEADER_H void ledon(); #endif Compiling with Visual Studio 2008 (kuukkeli) http://pnotepad.org/forums/topic/430#post-1592 Wed, 30 Jul 2008 11:46:02 +0000 kuukkeli 1592@http://pnotepad.org/forums/ Like you said, everything SHOULD have worked :) Instead though I got a bunch of <code>unresolved externals</code>. Here's the whole error set from PyPN after the above changes: <pre><code>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</code></pre> Compiling with Visual Studio 2008 (simon) http://pnotepad.org/forums/topic/430#post-1591 Tue, 29 Jul 2008 22:26:29 +0000 simon 1591@http://pnotepad.org/forums/ Ah, lightbulb moment! The project is set to link to that DLL by the inclusion of <code>boost_python-vc80-mt-gd-1_35.lib</code> 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. Compiling with Visual Studio 2008 (kuukkeli) http://pnotepad.org/forums/topic/430#post-1590 Mon, 28 Jul 2008 20:25:32 +0000 kuukkeli 1590@http://pnotepad.org/forums/ Concerning option 1: I already have <code>boost_python-vc90-mt-gd-1_35.dll</code> and <code>boost_python-vc90-mt-gd-1_35.lib</code> in <code>lib\boost-python-2.5</code> 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 <code>boost_python-vc80-mt-gd-1_35.dll</code> still end up in the <code>bin</code> directory while compiling requires vc90 version (if I replace it with vc90 version I get an error than vc80 version isn't found)? Compiling with Visual Studio 2008 (simon) http://pnotepad.org/forums/topic/430#post-1589 Mon, 28 Jul 2008 19:17:20 +0000 simon 1589@http://pnotepad.org/forums/ 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: <ol> <li>Build boost python for vc90 and use that </li> <li>Download a copy of the 2005 DebugCRT and install it, that should work ok but no guarantees </li> <li>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.</li> </ol> Compiling with Visual Studio 2008 (kuukkeli) http://pnotepad.org/forums/topic/430#post-1588 Mon, 28 Jul 2008 18:34:21 +0000 kuukkeli 1588@http://pnotepad.org/forums/ Assuming I did it correctly this is the debugger output concerning PyPN: <pre><code>'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'</code></pre> Does it ring any bells for you (I'm, as expected, drawing a blank)? Compiling with Visual Studio 2008 (simon) http://pnotepad.org/forums/topic/430#post-1585 Sun, 27 Jul 2008 20:39:29 +0000 simon 1585@http://pnotepad.org/forums/ 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. Compiling with Visual Studio 2008 (kuukkeli) http://pnotepad.org/forums/topic/430#post-1584 Fri, 25 Jul 2008 20:15:40 +0000 kuukkeli 1584@http://pnotepad.org/forums/ First, two more fixes. In file <code>actests.cpp</code> there are two more imports with extra <code>pnwtl</code>: <pre><code>#include "../pnwtl/autocomplete.h" #include "../pnwtl/pnstrings.h"</code></pre> 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 <code>bin</code>. Thanks for all the help this far. Compiling with Visual Studio 2008 (simon) http://pnotepad.org/forums/topic/430#post-1580 Fri, 25 Jul 2008 12:50:03 +0000 simon 1580@http://pnotepad.org/forums/ Thanks, I fixed the allocator and string thing, they should have been: <pre><code>#include "../allocator.h" #include "../pnextstring.h"</code></pre> 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: <pre><code>bin |- pypn | |- decorators.py |- scripts |- schemes |- taggers</code></pre> 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 <code>NTDDI_WIN6</code> even defined in your environment? Compiling with Visual Studio 2008 (kuukkeli) http://pnotepad.org/forums/topic/430#post-1574 Thu, 24 Jul 2008 04:53:45 +0000 kuukkeli 1574@http://pnotepad.org/forums/ 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 <code>GetThemeSysFont</code> I ended up commenting out the whole if-else part and left only <code>::GetThemeSysFont(m_winTheme, TMT_SMALLCAPTIONFONT, &lf);</code> in its place. Just changing <code>NTDDI_WIN6SP1</code> to <code>NTDDI_WIN6</code> 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 (<code>ctagsnavigator</code>, <code>pypn</code>). For <code>pypn</code> I also had to replace the Python related include with full path to <code>\Python25\include</code> library as it didn't find it otherwise and add vc90 boost files to <code>\lib\boost-python-2.5</code>. And finally I had to change <code>atlres.h</code> in <code>pn.rc</code> to full path to that file. With the above changes PN compiles and works. Project <code>tests</code> still gives errors though because of the following: <pre><code>#include "../pnwtl/allocator.h" #include "../pnwtl/string.h"</code></pre> These two files don't exist. I can fix the first by dropping <code>pnwtl</code> from the path but there's no obvious fix to second. My main concern though is the fact that while <code>pypn</code> compiles without errors or warnings it doesn't work. PN doesn't find it at all. I made <code>config.xml</code> for it and it finds <code>ctags</code> correctly but <code>pypn</code> doesn't show up. I copied the <code>pypn</code> and <code>scripts</code> folders from svn to PN's home directory but it made no difference. I have no idea how to make <code>pypn</code> work. Compiling with Visual Studio 2008 (simon) http://pnotepad.org/forums/topic/430#post-1552 Thu, 17 Jul 2008 08:00:02 +0000 simon 1552@http://pnotepad.org/forums/ jumpfroggy has put an excellent summary of the current build steps here: <a href="http://pnotepad.org/docs/dev/how_to_compile_pn" rel="nofollow">http://pnotepad.org/docs/dev/how_to_compile_pn</a> 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. Compiling with Visual Studio 2008 (jumpfroggy) http://pnotepad.org/forums/topic/430#post-1546 Wed, 16 Jul 2008 06:11:46 +0000 jumpfroggy 1546@http://pnotepad.org/forums/ 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! Compiling with Visual Studio 2008 (simon) http://pnotepad.org/forums/topic/430#post-1530 Tue, 08 Jul 2008 18:47:31 +0000 simon 1530@http://pnotepad.org/forums/ GetThemeSysFont: The bit of code we're looking at is this: <pre><code>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</code></pre> 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 <code>LOGFONT</code> instead of <code>LOGFONTW</code> which is what they really wanted (so <code>LOGFONTW</code> is cast to <code>LOGFONT</code>). I suspect that instead of <code>NTDDI_WIN6SP1</code> we want something earlier, perhaps you could see if <code>NTDDI_WIN6</code> 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. Compiling with Visual Studio 2008 (kuukkeli) http://pnotepad.org/forums/topic/430#post-1519 Thu, 03 Jul 2008 18:37:24 +0000 kuukkeli 1519@http://pnotepad.org/forums/ 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? Compiling with Visual Studio 2008 (simon) http://pnotepad.org/forums/topic/430#post-1518 Thu, 03 Jul 2008 16:34:24 +0000 simon 1518@http://pnotepad.org/forums/ 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.