406414 - Problem compiling for nsIMsgDBView support due to rule ordering issues in mail/build.mk

Status: RESOLVED FIXED

(Thunderbird :: Build Config, defect)

Description

[Christian Haider]

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; FDM; .NET CLR 1.1.4322)
Build Identifier: version 3.0a1pre (2007120112)

The problem is that if you try to build your own component which needs i.e. nsIMsgDBView.h the build stops. nsIMsgDBView is included in msgbase. Unfortunately msgbase isn't created yet. The solution is to change mail/build.mk.
Please find the solution attached thx to "standard8".

Reproducible: Always

Steps to Reproduce:
1. include own extension which needs nsIMsgDBView.h
2. build everything
3.
Actual Results:  
build stops with error:
fatal error C1083: Cannot open include file: 'nsIMsgDBView.h': No such file or directory

Expected Results:  
successful build

Comment 1

[Christian Haider]

Attachment: the changed build.mk. The diffence to the "old" one is that extensions is moved between mailnews and mail.

Comment 2

[Christian Haider]

Attachment: Example extensin which produeces the error. Extension if far from working but it should build. at least on windows.

Comment 3

[Magnus Melin [:mkmelin]]

Please attach a diff, not the complete new file. gStand in the mozilla dir and do cvs diff -up9

You also need to get the reviewed, see http://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree

Comment 4

[Christian Haider]

Attachment: This is the output of the diff. Hopefully that's the right way to post it.

Comment 5

[Benjamin Smedberg]

Comment on attachment 291089 [details] [diff] [review]
This is the output of the diff. Hopefully that's the right way to post it.

Looks ok to me, but a mailnews owner should give moa as well

Comment 6

[Reed Loden [:reed]]

Checking in mail/build.mk;
/cvsroot/mozilla/mail/build.mk,v  <--  build.mk
new revision: 1.5; previous revision: 1.4
done

Comment 7

[Christian Haider]

Bug 444686 undid this change. the problem reappeared

Comment 8

[Mark Banner (:standard8)]

Please don't re-open old bugs that were fixed. Please file a new bug - then we can track regression points better.