vs.net 2003
Romulus Marius Mare
that I am sure that vs.net 2003 compiler is much better than the original
compiler, so I am trying to use it. However this error looks like the
configuration tests are not recognizing the new compilers, hence the error.
It should be something very easy, and if someone gives me a hint how to
convice the make files to build, I am willing to test.
C:\dev\sources\other\Mozilla\mozilla>make -s -f client.mk build
cd /cygdrive/c/dev/sources/other/Mozilla/mozilla
/cygdrive/c/dev/sources/other/Mozilla/mozilla/configure
loading cache ./config.cache
checking host system type... i586-pc-msvc
checking target system type... i586-pc-msvc
checking build system type... i586-pc-msvc
checking for gcc... (cached) cl
checking whether the C compiler (cl ) works... yes
checking whether the C compiler (cl ) is a cross-compiler... no
checking whether we are using GNU C... (cached) no
checking whether cl accepts -g... (cached) no
checking for c++... (cached) cl
checking whether the C++ compiler (cl ) works... yes
checking whether the C++ compiler (cl ) is a cross-compiler... no
checking whether we are using GNU C++... (cached) no
checking whether cl accepts -g... (cached) no
checking for ranlib... (cached) ranlib
checking for ml... (cached) /cygdrive/c/dev/apps/vs.net/VC7/BIN/ml
checking for ar... (cached) ar
checking for ld... (cached) link
checking for strip... (cached) strip
checking for windres... (cached) windres
checking for midl... (cached) midl
configure: error: $(CXX) test failed. You must have MS VC++ in your path to
bui
ld.
*** Fix above errors and then restart with "make -f client.mk build"
make: *** [/cygdrive/c/dev/sources/other/Mozilla/mozilla/Makefile] Error 1
Thanks,
Romulus
Romulus Marius Mare
and midl compiler and started a new build with vs.net 2003.
So far I could not encounter any critical compiler errors, just more
warnings (which I believe can be easily eliminated) but...
It seems that the build crashes at some point because of the glib & libIDL
libraries. I used the vc7 libs for vs.net which, I think is the main
problem. mozilla developers should provide new versions for vc71.
Is anyone knowing who is the guy in charge with Mozilla win32 builds?
Romulus
PS are my messages off-topic? Having no replies to my messages makes me
believe that no one is interested in this subject. Is this correct or just
there are not so many around here to read them?
Christopher Seawood
> It seems that the build crashes at some point because of the glib & libIDL
> libraries. I used the vc7 libs for vs.net which, I think is the main
> problem. mozilla developers should provide new versions for vc71.
Or we could start requiring that people find/create their own binary
copies of glib & libIDL if binary compatibility is going to become an
issue with the win32 compilers. You'll note that we don't provide
binary versions on other platforms.
> Is anyone knowing who is the guy in charge with Mozilla win32 builds?
There is no one person in charge of the win32 builds. Posting here is
probably your best bet for finding someone interested in contributing
vc71 builds of the libraries.
> PS are my messages off-topic? Having no replies to my messages makes me
> believe that no one is interested in this subject. Is this correct or just
> there are not so many around here to read them?
The messages are on-topic. However, at this point, building with vs.net
2003 is unsupported/untested so it's unlikely that many people know how
to answer your questions.
- cls
Romulus Marius Mare
for mozilla. It seems so hard to get some attention. See below my comments.
"Christopher Seawood" <c...@seawood.org> wrote in message
news:ba9isr$ce...@ripley.netscape.com...
> Romulus Marius Mare wrote:
>
> > It seems that the build crashes at some point because of the glib &
libIDL
> > libraries. I used the vc7 libs for vs.net which, I think is the main
> > problem. mozilla developers should provide new versions for vc71.
>
> Or we could start requiring that people find/create their own binary
> copies of glib & libIDL if binary compatibility is going to become an
> issue with the win32 compilers. You'll note that we don't provide
> binary versions on other platforms.
Even better. How do I create my own binary copy of glib and libIDL? I could
not agree more with you that this is the way to go. I just need some hints
to get me started on the right direction. Actually I thought you *want* to
provide these two libraries only in binary form.
> > Is anyone knowing who is the guy in charge with Mozilla win32 builds?
>
> There is no one person in charge of the win32 builds. Posting here is
> probably your best bet for finding someone interested in contributing
> vc71 builds of the libraries.
True, but when no one replies for weeks, this is not of much help.
> > PS are my messages off-topic? Having no replies to my messages makes me
> > believe that no one is interested in this subject. Is this correct or
just
> > there are not so many around here to read them?
>
> The messages are on-topic. However, at this point, building with vs.net
> 2003 is unsupported/untested so it's unlikely that many people know how
> to answer your questions.
I cannot believe win32 mozilla builds are supported and nobody knows little
bits of info so I can get started. My exact point was that with little help,
I will try to document the mozilla build and changes with vc71. I can do
that along with other things I can do for mozilla.
Your reply is proving it, thanks again!
Romulus
Christopher Seawood
> Thanks! Finally I have one reply. I was just about to give up on developing
> for mozilla. It seems so hard to get some attention. See below my comments.
If you're seriously interested in developing for Mozilla, you need to be
a bit more patient and perhaps more persistent in your efforts to
discover answers for yourself.
> "Christopher Seawood" <c...@seawood.org> wrote in message
> news:ba9isr$ce...@ripley.netscape.com...
>
>>Romulus Marius Mare wrote:
>>
>>
>>>It seems that the build crashes at some point because of the glib &
>
> libIDL
>
>>>libraries. I used the vc7 libs for vs.net which, I think is the main
>>>problem. mozilla developers should provide new versions for vc71.
>>
>>Or we could start requiring that people find/create their own binary
>>copies of glib & libIDL if binary compatibility is going to become an
>>issue with the win32 compilers. You'll note that we don't provide
>>binary versions on other platforms.
>
>
> Even better. How do I create my own binary copy of glib and libIDL? I
You read the build instructions inside the source tarballs for glib &
libIDL. It was fairly straight forward last time I looked at it.
> could
> not agree more with you that this is the way to go. I just need some hints
> to get me started on the right direction. Actually I thought you *want* to
> provide these two libraries only in binary form.
Why should mozilla.org provide binaries for these libraries? They are
external dependencies. While having the binaries available is
convenient, it should not be mozilla.org's responsibility to make them
available.
Long ago someone thought it would be a Good Idea(tm) to provide binaries
for these libraries. Presumably, the reason for this was to lower the
boundary for letting people contribute to Mozilla on win320.
Unfortunately, this had the side-effect of making mozilla.org the
distributor for those libraries and now people expect that mozilla.org
should be providing future variants of the libraries.
>
>>>Is anyone knowing who is the guy in charge with Mozilla win32 builds?
>>
>>There is no one person in charge of the win32 builds. Posting here is
>>probably your best bet for finding someone interested in contributing
>>vc71 builds of the libraries.
>
>
> True, but when no one replies for weeks, this is not of much help.
Then it means that either no one is interested in the problem, knows the
solution for the problem or is unavailable to answer the question. That
should have been obvious. At that point, you should take a more
pro-active approach to helping yourself rather than comment about how
others aren't helping you.
>
>>>PS are my messages off-topic? Having no replies to my messages makes me
>>>believe that no one is interested in this subject. Is this correct or
>
> just
>
>>>there are not so many around here to read them?
>>
>>The messages are on-topic. However, at this point, building with vs.net
>>2003 is unsupported/untested so it's unlikely that many people know how
>>to answer your questions.
>
>
> I cannot believe win32 mozilla builds are supported and nobody knows little
> bits of info so I can get started.
Since not all win32 binaries are compatible any longer, you have to be
more specific about "supported win32 builds". VC60 and VC70 builds are
supported. VC71 builds are not.
- cls
Romulus Marius Mare
> solution for the problem or is unavailable to answer the question. That
> should have been obvious. At that point, you should take a more
> pro-active approach to helping yourself rather than comment about how
> others aren't helping you.
>
Cristopher, I am a bit surprised... Help myself?!? I can easily do that, but
I wanted to help the Mozilla community with something, I can offer. Some
directions from start *are* required, or so I feel granted the mozilla's
dimensions, and who should give these directions if not the community
itself. If this community is not very helpful, it means they are not
interested in my help, and in turn this means I have no interest in mozilla.
I do not need to build mozilla, I do not need to get involved, etc. I though
I may be of *some* help. Why should I keep then my mobile workstation's
harddisk occupied with some 4Gb of sources, tools and etc? Why should I get
involved if no one cares?
And to my shame, until you said in your first post, that I should build my
own glib and libidl binaries, I HAD NO IDEA that these are external
dependencies or what are they. I simply assumed that these are internal
libraries provided by mozilla. I downloaded now the sources for these
libraries and started to build them myself. Now I know, but I simply needed
your post to understand this. Mozilla's build instructions are not
supporting vc71. I did not even said otherwise. I simply said that it is
very odd, since this compiler is *way* better than vc6 (not even close to
the standard) and vc70 (very buggy).
However your answer above, makes me rethink my approach to Mozilla. I
assumed too many things about this community and now I am very disappointed
to understand the reality. I do not want such a community, too busy to have
time help each other. I can invest my free time in projects where the
community makes me feel welcomed, not telling me: go dig yourself and do not
ask others for help. There are so many guys, again an assumptions, building
mozilla or developing for win32... They are too busy digging themselves, to
have time to welcome others to the project, even it would take minutes of
their time. No wonder, some things are like they are.
I also assumed wrongly that mozilla.org may have an interest in using vc71
compiler, and I was offering my help. Boy, hat a wrong assumption, your
words above cleared me of any doubts!
I want to honestly thank you for your time Cristopher, and I just wish
Mozilla.org will rethink its approach when it comes to attracting volunteers
into project.
Romulus
us...@domain.invalid
Kees van der Burg
Hello Romulus,
I ran into the same building problems (using VC71). Did manage to build
the glib and idlLIB libraries with VC71?
I could use some help with it.
Tanx in advance.
Kees