The source code of virtualbox 6.1.18 already contains openssl and curl, so there is no need to compile separately

[SquallATF]

As the title

[CaptainFlint]

Unfortunately, I didn't manage to understand how to use these included sources of OpenSSL and cURL. They still have to be compiled, one way or another. Maybe there exists some way to force the build scripts to use the sources directly, but I don't know it. Besides, the configure.vbs script specifically searches for the compiled binaries, not the source files. And if there are no binaries, it fails. You can patch it, of course, but the fact it's written like that implies, that it is the preferred way (at least, for outside-of-Oracle developers).

In any case, compiling these projects separately has the advantages that:

1. you can update the libraries yourself (for example, if a new version was released with security fixes which you'd like to have);
2. it's much easier to split such a big project in pieces and deal with each piece independently. If you try to build it all at once, and something fails, it can be extremely hard to find out what went wrong, and where the source of the issue lies: in the library, in VBox, in build scrips, in makefiles...

[SquallATF]

Sorry, I did not run configure.vbs before build, Just copy old config to new verson and manual remove openssl and curl config from AutoConfig.kmk.
To make builtin source work should modify configure.vbs and remove line from 2281 to 2290 to skip openssl and curl check.

   CheckForSsl strOptSsl, False
   if g_strTargetArch = "amd64" then
       ' 32-bit openssl required as well
       CheckForSsl strOptSsl32, True
   end if
   CheckForCurl strOptCurl, False
   if g_strTargetArch = "amd64" then
       ' 32-bit Curl required as well
       CheckForCurl strOptCurl32, True
   end if

[arminanton]

were you able to build version vbox 7.0.4 for windows 11? (or even win 10)

so, if you skip configure.vbs, and considering you don't have the old config to copy from, did you simply jump to env.bat then kmk?

[CaptainFlint]

@SquallATF
Sorry it took so long, but your suggestion worked, and I've been building VBox like that for a while. Although I didn't have free time to update the article, that's why I didn't report it earlier. Now I finally was able to do it; the updated version of the article has been committed.

@arminanton
I'm currently looking into building the latest version 7.0.10. The configure.vbs part is the easiest one, the main problem lies in the actual building. It required creating a completely new environment from scratch, many tools have changed dramatically, some new ones were added, and needed to be learned. So it wasn't a one-night task. But I finally managed to find time for it, and by now I've even been able to reach the fully built distribution. There's still a lot of work to be done: I haven't even attempted to install it, so I have no idea if it will even start. I will need to check how it works, and compare it to the Oracle version, to see if anything is missing. And also I only have it test-signed, and I need to investigate how they changed their driver signing scripts, so that they could be used properly by those who have access to the proper certificate. Not to mention all this has to be described properly in the article. So it will be a while longer before the instruction for version 7 is ready. But it's on the way.

[arminanton]

That is awesome @CaptainFlint !! I am hoping to be able to build that and also build the driver installation package too (the one that we later use to mount as an iso file into our VMs). I plan to customize those drivers later on.

[CaptainFlint]

Unfortunately, I don't have any plans in building the guest drivers myself, if that's what you mean. Like before, I simply download the guest additions ISO that Oracle provides. I only rebuild the host drivers.

[arminanton]

No worries. Being able to build the latest version to achieve compatibility with win 10/11 is awesome already! I'm seeking to have a host windows vm with custom drivers, with custom names and paths on them, mostly to bypass those script that check if you are running a vm or not. Before, changing the description of the driver on regedit was good enough, but nowadays they check for any 'virtualbox' or 'vbox' or anything related to that in the registry.

[arminanton]

@CaptainFlint Let me know if I can help with anything there :)

[CaptainFlint]

@arminanton Thank you, but I don't think you can. I did manage to build 7.0 successfully a while ago (I have not tested it extensively, but seems to be OK). However, before I could finish rewriting the article for the new steps and requirements, I had quite a chunk of other important stuff dropped onto me, and had to postpone the article for a while. I'll finish it some day.