Building VirtualBox OSE 32 bit (SVN) with VS2010
-
- Volunteer
- Posts: 321
- Joined: 7. Oct 2009, 12:40
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: various
Re: Building VirtualBox OSE 32 bit (SVN) with VS2010
That's right.
Re: Building VirtualBox OSE 32 bit (SVN) with VS2010
Same error keeps coming.
Cannot open include file: 'openssl/md5.h': No such file or directory
I have downloaded the source zip. Extracted it in a folder and built it using precompiled Autoconfig.kmk and env.bat.
All the required paths are specified properly. I have verified it. Please someone help me if the have any idea regarding this issue.
Cannot open include file: 'openssl/md5.h': No such file or directory
I have downloaded the source zip. Extracted it in a folder and built it using precompiled Autoconfig.kmk and env.bat.
All the required paths are specified properly. I have verified it. Please someone help me if the have any idea regarding this issue.
-
- Volunteer
- Posts: 321
- Joined: 7. Oct 2009, 12:40
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: various
Re: Building VirtualBox OSE 32 bit (SVN) with VS2010
You need to provide the 32 bit openssl and curl versions to build the 64 bit VirtualBox OSE. I always add some required entries to AutoConfig.kmk, after it has been generated by configure.vbs (see the lines containing LIBCURL-x86 and OPENSSL-x86, in the attached file).
- Attachments
-
- AutoConfig.zip
- (1.02 KiB) Downloaded 116 times
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Building VirtualBox OSE 32 bit (SVN) with VS2010
I might point out that specific locations or other requirements that you need to add to the AutoConfig.kmk after it runs can and should be added to the LocalConfig.kmk instead so editing would not be necessary. Create the LocalConfig.kmk as it probably does not exist and save in the top level folder/directory of your build.
Examples:
Examples:
Code: Select all
# specifying a special version of gsoap and enabling it.
VBOX_GSOAP_INSTALLED := 1
VBOX_PATH_GSOAP := /Home/<user>/gsoap
VBOX_PATH_GSOAP_BIN := /Home/<user>/gsoap/bin
# specifying a special version of java
VBOX_JAVA_HOME := /usr/lib/jvm/java-6-openjdk-amd64
Re: Building VirtualBox OSE 32 bit (SVN) with VS2010
This is the Autoconfig file that I am using. Helpertools mentioned it in it is contained with source folde and hence the path goes as ..\Helpertools. This Helpertools directory in turn contains the binaries for all the dependencies: openssl,curl,sdl,mingw and qt. Please take a look into it if possible and suggest if any changes might help. VBoxRTDeps is the one at which build stucks always. openssl/md5.h same error keeps coming.
- Attachments
-
- AutoConfig.zip
- (1.5 KiB) Downloaded 78 times
-
- Volunteer
- Posts: 321
- Joined: 7. Oct 2009, 12:40
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: various
Re: Building VirtualBox OSE 32 bit (SVN) with VS2010
There are no OPENSSL-x86 and LIBCURL-x86 entires in your file. Check again.
Re: Building VirtualBox OSE 32 bit (SVN) with VS2010
Its there from line 31st there are entries for x86
PATH_SDK_LIBSDL.x86 := $(PATH_HELPER_TOOLS)/x86/SDL-1.2.15
SDK_VBOX_OPENSSL_INCS.x86 := $(PATH_HELPER_TOOLS)/x86/openssl-0.98k/include
SDK_VBOX_OPENSSL_LIBS.x86 := $(PATH_HELPER_TOOLS)/x86/openssl-0.98k/lib/ssleay32.lib $(PATH_HELPER_TOOLS)/x86/openssl-0.98k/lib/libeay32.lib
SDK_VBOX_BLD_OPENSSL_LIBS.x86 := $(PATH_HELPER_TOOLS)/x86/openssl-0.98k/lib/ssleay32.lib $(PATH_HELPER_TOOLS)/x86/openssl-0.98k/lib/libeay32.lib
SDK_VBOX_LIBCURL_INCS.x86 := $(PATH_HELPER_TOOLS)/x86/libcurl/include
SDK_VBOX_LIBCURL_LIBS.x86 := $(PATH_HELPER_TOOLS)/x86/libcurl/libcurl.lib
VBOX_PATH_DIFX.x86 := $(PATH_SDK_WINDDK71)/redist/DIFx/DIFxAPI/x86
PATH_SDK_QT4.x86 := $(PATH_HELPER_TOOLS)/x86/Qt.x86/4.8.3
Do I actually need it because I am building for x64. Anyways I do have the x86 entries
PATH_SDK_LIBSDL.x86 := $(PATH_HELPER_TOOLS)/x86/SDL-1.2.15
SDK_VBOX_OPENSSL_INCS.x86 := $(PATH_HELPER_TOOLS)/x86/openssl-0.98k/include
SDK_VBOX_OPENSSL_LIBS.x86 := $(PATH_HELPER_TOOLS)/x86/openssl-0.98k/lib/ssleay32.lib $(PATH_HELPER_TOOLS)/x86/openssl-0.98k/lib/libeay32.lib
SDK_VBOX_BLD_OPENSSL_LIBS.x86 := $(PATH_HELPER_TOOLS)/x86/openssl-0.98k/lib/ssleay32.lib $(PATH_HELPER_TOOLS)/x86/openssl-0.98k/lib/libeay32.lib
SDK_VBOX_LIBCURL_INCS.x86 := $(PATH_HELPER_TOOLS)/x86/libcurl/include
SDK_VBOX_LIBCURL_LIBS.x86 := $(PATH_HELPER_TOOLS)/x86/libcurl/libcurl.lib
VBOX_PATH_DIFX.x86 := $(PATH_SDK_WINDDK71)/redist/DIFx/DIFxAPI/x86
PATH_SDK_QT4.x86 := $(PATH_HELPER_TOOLS)/x86/Qt.x86/4.8.3
Do I actually need it because I am building for x64. Anyways I do have the x86 entries
-
- Volunteer
- Posts: 321
- Joined: 7. Oct 2009, 12:40
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: various
Re: Building VirtualBox OSE 32 bit (SVN) with VS2010
I'm talking about references such as:
SDK_VBOX_OPENSSL-x86_INCS
I don't think it's the same thing as what you're referring to:
SDK_VBOX_OPENSSL_INCS.x86
I can't find any connections between the two, in any of the kmk files.
Use Process Monitor from Sysinternals to find out what the build system is trying to access while it's trying to compile that piece.
SDK_VBOX_OPENSSL-x86_INCS
I don't think it's the same thing as what you're referring to:
SDK_VBOX_OPENSSL_INCS.x86
I can't find any connections between the two, in any of the kmk files.
Use Process Monitor from Sysinternals to find out what the build system is trying to access while it's trying to compile that piece.
Re: Building VirtualBox OSE 32 bit (SVN) with VS2010
idk man. I built 4.2.6 with the same Autoconfig.kmk and it built fine, except for VboxRem.dll all the binaries were built without any problem.
-
- Volunteer
- Posts: 321
- Joined: 7. Oct 2009, 12:40
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: various
Re: Building VirtualBox OSE 32 bit (SVN) with VS2010
There were changes made after 4.2.6. I think this was the bug report which led to this change, the need to build some 32 bit components for VirtualBox 64 bit. Like I said, OPENSSL-x86 is not the same as OPENSSL.
Re: Building VirtualBox OSE 32 bit (SVN) with VS2010
E:/VBOX_FRESH/vbox_svn/src/libs/Makefile.kmk:55: E:/VBOX_FRESH/vbox_svn/src/libs
/openssl-0.9.8t/Makefile.kmk: No such file or directory
kmk: *** No rule to make target `E:/VBOX_FRESH/vbox_svn/src/libs/openssl-0.9.8t/
Makefile.kmk'. Stop.
This is the error which comes up when I am trying to compile with Autoconfig.kmk which you gave me. Makefile.kmk has been same for 4.2.6 and 4.3 which is kept in (vbox_svn/src/libs/Makefile.kmk). 55th line is looking for openssl-0.9.8t/Makefile.kmk which is not htere but it was not there in previous cases also.If I need that where do I get it or do I need to update something else?
/openssl-0.9.8t/Makefile.kmk: No such file or directory
kmk: *** No rule to make target `E:/VBOX_FRESH/vbox_svn/src/libs/openssl-0.9.8t/
Makefile.kmk'. Stop.
This is the error which comes up when I am trying to compile with Autoconfig.kmk which you gave me. Makefile.kmk has been same for 4.2.6 and 4.3 which is kept in (vbox_svn/src/libs/Makefile.kmk). 55th line is looking for openssl-0.9.8t/Makefile.kmk which is not htere but it was not there in previous cases also.If I need that where do I get it or do I need to update something else?
-
- Volunteer
- Posts: 321
- Joined: 7. Oct 2009, 12:40
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: various
Re: Building VirtualBox OSE 32 bit (SVN) with VS2010
That means that one of the conditions at lines 52-54 are being met. Most likely SDK_VBOX_OPENSSL_INCS isn't properly set.
But I'm not sure what you're trying to build. In the VirtualBox 4.3.20 sources, that line is
It doesn't reference the 0.9.8 version.
But I'm not sure what you're trying to build. In the VirtualBox 4.3.20 sources, that line is
Code: Select all
include $(PATH_SUB_CURRENT)/openssl-1.0.1j/Makefile.kmk
Re: Building VirtualBox OSE 32 bit (SVN) with VS2010
E:\VBOX_FRESH\vbox_svn\src\VBox\Runtime\common\misc\http.cpp(250) : error C2065:
'CURLOPT_PROXYUSERNAME' : undeclared identifier
E:\VBOX_FRESH\vbox_svn\src\VBox\Runtime\common\misc\http.cpp(254) : error C2065:
'CURLOPT_PROXYPASSWORD' : undeclared identifierkBuild: Comp
iE:\VBOX_FRESH\vbox_svn\src\VBox\Runtime\common\misc\http.cpp(391) : error C2065
: 'CURLINFO_REDIRECT_URL' : undeclared identifierling VBoxRT-x86 -
This is the latest error that I am getting. Actually I am using openssl-0.9.8 so I changed the reference to it. It is all the same though, if I keep it as you said it gives the same error sayin openss1-1.0.1j instead of openssl-0.9.8. I am past it now and coming up with above mentioned fresh errors.
'CURLOPT_PROXYUSERNAME' : undeclared identifier
E:\VBOX_FRESH\vbox_svn\src\VBox\Runtime\common\misc\http.cpp(254) : error C2065:
'CURLOPT_PROXYPASSWORD' : undeclared identifierkBuild: Comp
iE:\VBOX_FRESH\vbox_svn\src\VBox\Runtime\common\misc\http.cpp(391) : error C2065
: 'CURLINFO_REDIRECT_URL' : undeclared identifierling VBoxRT-x86 -
This is the latest error that I am getting. Actually I am using openssl-0.9.8 so I changed the reference to it. It is all the same though, if I keep it as you said it gives the same error sayin openss1-1.0.1j instead of openssl-0.9.8. I am past it now and coming up with above mentioned fresh errors.
Re: Building VirtualBox OSE 32 bit (SVN) with VS2010
Do you know about this error..It keeps coming..Although if I use my Autoconfig.kmk this error does not come up but openssl/md5.h error comes up. May be something wrong with Autoconfig.kmk because changing it seems to somehow rectify this particular error (http.cpp)
-
- Volunteer
- Posts: 321
- Joined: 7. Oct 2009, 12:40
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: various
Re: Building VirtualBox OSE 32 bit (SVN) with VS2010
Probably the curl include path is set incorrectly. Check the failing command line for clues.
Out of curiosity, why do you need to compile VirtualBox?
Out of curiosity, why do you need to compile VirtualBox?