On Friday, 28 January 2022 at 22:45:31 UTC, forkit wrote:
> On Friday, 28 January 2022 at 22:35:14 UTC, max haughton wrote:
>>
>> I can't help if you don't say what you've actually tried to do. I haven't actually worked on D directly from windows for a while now so I can only fix things that are broken or point you in the right way rather than dictating what you are to do (in part because I'm not a slave)
>
> As a systems admin/engineer, I build production systems from scratch.
>
> They are **guaranteed** to work, as defined.
>
> I can provide the instruction/scripts to others, they can run them, and they WILL work... ** guaranteed **
>
> That's the approach I want to take here (as opposed to the approach your suggesting, which starts from an existing system, and which for me, has just wasted too many hours of my life that I cannot get back).

As a human being writing at 11PM I am willing to help but I cannot do so without something to go on. You should readily have this information to hand since you guarantee it doesn't work.

As an engineer you should also know how to communicate information effectively to solve a problem faster, you currently aren't doing this.

On Friday, 28 January 2022 at 23:07:25 UTC, max haughton wrote:
>
> As a human being writing at 11PM I am willing to help but I cannot do so without something to go on. You should readily have this information to hand since you guarantee it doesn't work.
>
> As an engineer you should also know how to communicate information effectively to solve a problem faster, you currently aren't doing this.

C'mon...you're really missing the point here.

I want to take a different approach. Not your approach.

That should be clear by now.

I want to start with 'nothing'. Clean! Then take a step-by-step approach to building the system.

I do not want to start with a system that is already in operation, with who knows what on it.

> As a human being writing at 11PM I am willing to help but I cannot do so without something to go on. You should readily have this information to hand since you guarantee it doesn't work.

So to your point, there is 'nothing to go on'. I'm starting with 'nothing'.

On Friday, 28 January 2022 at 22:52:57 UTC, Steven Schveighoffer wrote:
>
> I have to be honest, most people here don't build the compiler or runtime/phobos, and those that do usually are developing on Linux or Mac. So you are likely to get more traction with "I'm here, it doesn't work, please help" than wishing for a person who has the magic recipe.
>

I think it's completely logical to ask, if someone already has the 'magic' recipe, before I go off experimenting myself ;-)

Of course, I don't expect that anyone actually has it.

I do expect to spend a lot of time on this myself. But that is worthwhile, if what I end up with, is a recipe I can give to others, that will also result in what the recipe says it makes.. guaranteed.

Again. I do NOT want to start with an existing system with god knows what on it that would cause god knows what problem with god knows what part of the process.

On Friday, 28 January 2022 at 22:55:17 UTC, MoonlightSentinel wrote:
> As others have said before, steps + error messages would be appreciated s.t. we can determine whether it's a local or general issue.
>
Nope. Not going to do that. As explained ;-)

I'm taking the alternative path I've laid out.

> Software:
> - Any VS version (already used 17 and 22 but others should work as well)
> - DM make

Thanks. This is information I can actually work with ;-)

On Friday, 28 January 2022 at 22:55:17 UTC, MoonlightSentinel wrote:
>
> ...
> Software:
> - Any VS version (already used 17 and 22 but others should work as well)

I presume you mean the 'build tool' only? Do you know precisely what components are needed?

I'm thinking that I will begin this 'recipe', using a the 'Windows Server Core' image.

So I have 'Step 1' almost complete ;-)

On Friday, 28 January 2022 at 23:46:10 UTC, forkit wrote:
>
> I'm thinking that I will begin this 'recipe', using a the 'Windows Server Core' image.

no. scratch that. going to build a desktop system instead.

ideally all steps will be done for an 'offline' system, using software that does not 'require' access to the internet in order to work.

(i.e. need to download what is required outside of the system, and install it manually)

Step1: clean install of Windows 7 SP1 (KB976932) plus Update (KB976902)
Step2: clean install of .NET Framework 4.7.3 (which also installs KB4019990 )
Step3: install certificates need for installing VS buildtools 2019 16.11
Step4: install VS buildtools 2019 16.11 (ensuring the following components selected)
    ..
    ...
    ....

On Saturday, 29 January 2022 at 01:26:56 UTC, zjh wrote:
> On Saturday, 29 January 2022 at 00:27:28 UTC, forkit wrote:
>
>
> `must be` win10!

yeah... sadly, I'll have to start with that I guess (since almost everyone will want to start with that ;-)

still trying to take-apart this command 'dub run digger'.. wtf is it doing ... I gotta work that out first :-(

On Friday, 28 January 2022 at 21:39:39 UTC, forkit wrote:
> No matter what instructions, blogs, articles... I use.. I simply cannot manage to build druntime,dmd,phobos, from source on Windows.
>
> Of course, building from source in linux is a breeze.
>
> But I cannot test my changes on Windows, cause I cannot build from source on Windows!
>
> Does anyone have a step-by-step process, that is 'guaranteed' to work? (with as few unnecessary dependencies as possible please).
>
> I'm happy to build a dedicated build machine for this purpose, with just the software needed to build from source.
>
> NOTE: I said 'guaranteed' to work ;-)  ... I've wasted to much time following instructions that just do not work.

Hi,
I used this for building on windows, it works wonders for me.

https://github.com/rainers/dlangvs

- Alex

On 29/01/2022 3:07 PM, forkit wrote:
> still trying to take-apart this command 'dub run digger'.. wtf is it doing ... I gotta work that out first :-(

Step 1: Download digger + dependencies
Step 2: Compile digger
Step 3: Run digger

https://github.com/CyberShadow/Digger/blob/master/dub.sdl

Pretty straight forward as far as digger itself is concerned.