MantisBT - Doomseeker
View Issue Details
0002468Doomseeker[All Projects] Suggestionpublic2015-09-25 13:472015-11-20 17:52
WhiteMagicRaven 
Zalewa 
normalminorhave not tried
closedinvalid 
MicrosoftWindowsXP/Vista/7
1.0 
 
0002468: HOW TO COMPILE doomseeker plugins
HOW TO COMPILE doomseeker plugins
No tags attached.
Issue History
2015-09-25 13:47WhiteMagicRavenNew Issue
2015-09-25 13:55WhiteMagicRavenNote Added: 0013551
2015-09-25 18:32ZalewaNote Added: 0013553
2015-09-25 18:36ZalewaNote Edited: 0013553bug_revision_view_page.php?bugnote_id=13553#r8077
2015-09-30 19:00ZalewaNote Added: 0013569
2015-10-01 14:28WhiteMagicRavenNote Added: 0013571
2015-10-10 22:03WhiteMagicRavenNote Added: 0013655
2015-10-10 22:08WhiteMagicRavenNote Edited: 0013655bug_revision_view_page.php?bugnote_id=13655#r8133
2015-10-10 22:13WhiteMagicRavenNote Edited: 0013655bug_revision_view_page.php?bugnote_id=13655#r8134
2015-10-11 00:04ZalewaNote Added: 0013658
2015-10-11 11:14WhiteMagicRavenNote Added: 0013660
2015-10-11 17:10WhiteMagicRavenNote Added: 0013662
2015-10-17 14:22WhiteMagicRavenNote Added: 0013676
2015-11-20 17:52ZalewaStatusnew => closed
2015-11-20 17:52ZalewaAssigned To => Zalewa
2015-11-20 17:52ZalewaResolutionopen => invalid

Notes
(0013551)
WhiteMagicRaven   
2015-09-25 13:55   
you dont have any windows compilation instructions and you dont have any contacts, sorry posting here
(0013553)
Zalewa   
2015-09-25 18:32   
(edited on: 2015-09-25 18:36)
Hi.

Compilation instructions for Windows are here:
'https://bitbucket.org/Blzut3/doomseeker/src/7ae7ffb022693dcbc90b16e02079f881cc31ee20/COMPILE.Windows.txt?at=default&fileviewer=file-view-default [^]'

If you find any problems while following these instructions I'd be obliged to hear from you so that the document can be improved.

Our contact emails are in about dialog. You can also contact us through bitbucket or here, on Zandronum page. No need to be sorry.

(0013569)
Zalewa   
2015-09-30 19:00   
WhiteMagicRaven, do you need any further assistance?
(0013571)
WhiteMagicRaven   
2015-10-01 14:28   
i think yes, wait, i just need to try everything my self
(0013655)
WhiteMagicRaven   
2015-10-10 22:03   
(edited on: 2015-10-10 22:13)
its necessary to use MSVC 2013? i have 2010.
2013 request to use iexplore10 and windows higher than win7, tried also in xp.
i have errors in cmake, also no where i used openssl, just unpacked.
i am thinking that i get not the latest source by link?
'https://bitbucket.org/Blzut3/doomseeker/get/1.0.tar.bz2 [^]'

'http://devbuilds.drdteam.org/doomseeker/ [^]'

Quote

DISCLAIMER
These are unofficial Mercurial builds. Remember these builds are beta-quality software - use at your own risk!

A log of recent HG activity can be seen here.
Bugs may be posted here. (here leads to'http://skulltag.net/forum/viewforum.php?f=210 [^]' dead link



Quote

Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR)
Could NOT find BZip2 (missing: BZIP2_LIBRARIES BZIP2_INCLUDE_DIR)
Using internal zlib
CMake Warning (dev) at zlib/CMakeLists.txt:65 (if):
  Policy CMP0054 is not set: Only interpret if() arguments as variables or
  keywords when unquoted. Run "cmake --help-policy CMP0054" for policy
  details. Use the cmake_policy command to set the policy and suppress this
  warning.

  Quoted variables like "MSVC" will no longer be dereferenced when the policy
  is set to NEW. Since the policy is not set the OLD behavior will be used.
This warning is for project developers. Use -Wno-dev to suppress it.

Using internal bzip2 library
CMake Warning (dev) at bzip2/CMakeLists.txt:3 (if):
  Policy CMP0054 is not set: Only interpret if() arguments as variables or
  keywords when unquoted. Run "cmake --help-policy CMP0054" for policy
  details. Use the cmake_policy command to set the policy and suppress this
  warning.

  Quoted variables like "MSVC" will no longer be dereferenced when the policy
  is set to NEW. Since the policy is not set the OLD behavior will be used.
This warning is for project developers. Use -Wno-dev to suppress it.

CMake Warning at CMakeLists.txt:68 (message):
  Full automatic packaging is only supported for Microsoft Visual C++ 2008.
  Remember that redist needs to be accessible both by the main program and by
  the engines/ directory. Copy over Manifest and redist DLLs to engines/
  directory if you do not plan on installing redist on target machines.


WARNING: you are using the obsolete 'PKGCONFIG' macro, use FindPkgConfig
WARNING: PKGCONFIG() indicates that the tool pkg-config has not been found on your system. You should install it.
CMake Warning (dev) at tools/updateinstaller/src/CMakeLists.txt:137 (get_property):
  Policy CMP0026 is not set: Disallow use of the LOCATION target property.
  Run "cmake --help-policy CMP0026" for policy details. Use the cmake_policy
  command to set the policy and suppress this warning.

  The LOCATION property should not be read from target "updater". Use the
  target name directly with add_custom_command, or use the generator
  expression $<TARGET_FILE>, as appropriate.

This warning is for project developers. Use -Wno-dev to suppress it.

CMake Warning (dev) at tools/updaterevision/CMakeLists.txt:4 (if):
  Policy CMP0054 is not set: Only interpret if() arguments as variables or
  keywords when unquoted. Run "cmake --help-policy CMP0054" for policy
  details. Use the cmake_policy command to set the policy and suppress this
  warning.

  Quoted variables like "MSVC" will no longer be dereferenced when the policy
  is set to NEW. Since the policy is not set the OLD behavior will be used.
This warning is for project developers. Use -Wno-dev to suppress it.

CMake Warning (dev) at tools/updaterevision/CMakeLists.txt:23 (get_target_property):
  Policy CMP0026 is not set: Disallow use of the LOCATION target property.
  Run "cmake --help-policy CMP0026" for policy details. Use the cmake_policy
  command to set the policy and suppress this warning.

  The LOCATION property should not be read from target "updaterevision". Use
  the target name directly with add_custom_command, or use the generator
  expression $<TARGET_FILE>, as appropriate.

This warning is for project developers. Use -Wno-dev to suppress it.

CMake Warning (dev) at src/core/CMakeLists.txt:26 (get_target_property):
  Policy CMP0026 is not set: Disallow use of the LOCATION target property.
  Run "cmake --help-policy CMP0026" for policy details. Use the cmake_policy
  command to set the policy and suppress this warning.

  The LOCATION property should not be read from target "updaterevision". Use
  the target name directly with add_custom_command, or use the generator
  expression $<TARGET_FILE>, as appropriate.

This warning is for project developers. Use -Wno-dev to suppress it.

CMake Error at C:/Program Files (x86)/CMake/share/cmake-3.3/Modules/FindQt4.cmake:1326 (message):
  Found unsuitable Qt version "5.5.0" from
  e:/chrome-downloads/Qt5.5.0-no-icu-Zalewa-VS2013-x86/Qt5.5.0-no-icu-Zalewa/bin/qmake.exe,
  this code requires Qt 4.x
Call Stack (most recent call first):
  src/core/CMakeLists.txt:34 (find_package)


Configuring incomplete, errors occurred!
See also "E:/doomseeker/CMakeFiles/CMakeOutput.log".
See also "E:/doomseeker/CMakeFiles/CMakeError.log".


(0013658)
Zalewa   
2015-10-11 00:04   
The link you provided isn't to the latest source. It's for the point of history of the source where Doomseeker 1.0 was released. You can download the latest version using either Mercurial, or going to "Download" section and using "Download repository" link.

Right now you're trying to build version 1.0 but you use newer instructions for latest version, which are not compatible. 1.0 still requires Qt 4.0 and we've moved away from that. In your downloaded source there is the same file with compilation instructions in its main directory. If you insist on compiling 1.0, you need to follow the instructions from this file to the letter. If you wish to compile the latest verion, you must follow the latest version of the file. Besides Qt 4.0, version 1.0 also requires Visual Studio 2008. Lastly, Visual Studio 2013 does run in Win7. I use Win7.
(0013660)
WhiteMagicRaven   
2015-10-11 11:14   
trying to compile in 2010 a zandronum plugin for example get error: 1>LINK : fatal error LNK1104: cannot open file '..\..\core\Debug\doomseeker.lib'
trying to search it not found.
trying compile doomseeker c/c++ compiler fatal error.
now downloading MSVC 2013 Express, from ms site slow =(
(0013662)
WhiteMagicRaven   
2015-10-11 17:10   
okay, i have win7 and use windows update it says win7 updated to sp1 but msvc keep telling "newer windows reaquried"
need to reinstall windows lol
(0013676)
WhiteMagicRaven   
2015-10-17 14:22   
i think this tutorial old too?
'http://doomseeker.drdteam.org/docs/plugins.php [^]'

did i can compile only libmyengine.dll and put it in doomseeker/engines folder?

but when i start doomseker it doesnot see my plugin, doomseeker knows about plugins ? plugins should be registered in doomseeker?

i can't start doomseeker compiled by me, error in picture ->'http://raven-05.narod.ru/ex/doomseeker.png [^]'