It would mean that a VisualD project for druntime, as well as a VisualC++ project for zlib, would be required. The issue I see is that while I know that Mono-D can open VisualD project files, as well as dub projects, and mono-d project files, I don't know if it can open VisualC++ project files, which would be required in order to build. I'm fairly certain that it can't build VisualC++ project files from a version of VS older than 2010, due to the fact that 2010 is the first version where VisualC++ projects were proper MSBuild project files.

On 5/8/14, Manu via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
> DMD has a VS project, is there an objection to one for phobos too?
>

On 8 May 2014 23:58, Orvid King via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
> It would mean that a VisualD project for druntime, as well as a VisualC++ project for zlib, would be required. The issue I see is that while I know that Mono-D can open VisualD project files, as well as dub projects, and mono-d project files, I don't know if it can open VisualC++ project files, which would be required in order to build. I'm fairly certain that it can't build VisualC++ project files from a version of VS older than 2010, due to the fact that 2010 is the first version where VisualC++ projects were proper MSBuild project files.

I'm fairly sure MonoDevelop can't open .vcxproj files. They have their
own .cproj format for C/C++.
But either way, the project is for Visual Studio. Surely the DMD VS
projects don't work in MonoDevelop either? I just wanted to see parity
with the DMD project files.
What do the DMD devs who use VS do when working on phobos?

Like, 9 out of 10 times I think I might do some work on phobos, I remember there's no project files and go and do something else.

On 9 May 2014 00:27, Manu <turkeyman@gmail.com> wrote:
> On 8 May 2014 23:58, Orvid King via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
>> It would mean that a VisualD project for druntime, as well as a VisualC++ project for zlib, would be required. The issue I see is that while I know that Mono-D can open VisualD project files, as well as dub projects, and mono-d project files, I don't know if it can open VisualC++ project files, which would be required in order to build. I'm fairly certain that it can't build VisualC++ project files from a version of VS older than 2010, due to the fact that 2010 is the first version where VisualC++ projects were proper MSBuild project files.
>
> I'm fairly sure MonoDevelop can't open .vcxproj files. They have their
> own .cproj format for C/C++.
> But either way, the project is for Visual Studio. Surely the DMD VS
> projects don't work in MonoDevelop either? I just wanted to see parity
> with the DMD project files.
> What do the DMD devs who use VS do when working on phobos?
>
> Like, 9 out of 10 times I think I might do some work on phobos, I remember there's no project files and go and do something else.

This:
$(LIB) : $(SRC_TO_COMPILE) \
  $(ZLIB) $(DRUNTIMELIB) win32.mak win64.mak
  $(DMD) -lib -of$(LIB) -Xfphobos.json $(DFLAGS) $(SRC_TO_COMPILE) \
    $(ZLIB) $(DRUNTIMELIB)

Trying to understand this bit... why is $(ZLIB) $(DRUNTIMELIB)
provided to the compiler? It's building the phobos lib right, not
linking anything?

On Thursday, 8 May 2014 at 15:23:35 UTC, Manu via Digitalmars-d wrote:
> Trying to understand this bit... why is $(ZLIB) $(DRUNTIMELIB)
> provided to the compiler? It's building the phobos lib right, not
> linking anything?

druntime and zlib are statically linked into Phobos

On 9 May 2014 01:38, Dicebot via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
> On Thursday, 8 May 2014 at 15:23:35 UTC, Manu via Digitalmars-d wrote:
>>
>> Trying to understand this bit... why is $(ZLIB) $(DRUNTIMELIB)
>> provided to the compiler? It's building the phobos lib right, not
>> linking anything?
>
>
> druntime and zlib are statically linked into Phobos

Oh right. I never noticed. I just presumed druntime was a separate lib. So... you always have to build druntime at the same time as phobos? Guess I need a project for that too.

Well, that explains why I'm getting these ctfe errors building phobos (trying to ctfe druntime code). Although I don't see in the phobos makefile where the compiler is being given the druntime import path...?

On Thursday, 8 May 2014 at 15:52:37 UTC, Manu via Digitalmars-d wrote:
> On 9 May 2014 01:38, Dicebot via Digitalmars-d
> <digitalmars-d@puremagic.com> wrote:
>> On Thursday, 8 May 2014 at 15:23:35 UTC, Manu via Digitalmars-d wrote:
>>>
>>> Trying to understand this bit... why is $(ZLIB) $(DRUNTIMELIB)
>>> provided to the compiler? It's building the phobos lib right, not
>>> linking anything?
>>
>>
>> druntime and zlib are statically linked into Phobos
>
> Oh right. I never noticed. I just presumed druntime was a separate lib.
> So... you always have to build druntime at the same time as phobos?
> Guess I need a project for that too.
>
> Well, that explains why I'm getting these ctfe errors building phobos
> (trying to ctfe druntime code). Although I don't see in the phobos
> makefile where the compiler is being given the druntime import
> path...?

posix.mak has DRUNTIME_PATH, don't know about Windows one

On Thursday, 8 May 2014 at 13:58:51 UTC, Orvid King via Digitalmars-d wrote:

> I'm fairly certain that it can't build VisualC++ project files from a version of VS older than 2010, due to the fact that 2010 is the first version where VisualC++ projects were proper MSBuild project files.

MSBuild can build VisualC++ 2008 project files, but you do have
to use a version of MSBuild that is happy with those files.

For those interested, more details can be found here:

http://www.zeusedit.com/zforum/viewtopic.php?t=7143