VS and MRef to forward declarations ?

[Cesc]

This was one of my problems when sometime ago i tried compilation with
Visual Embedded 4.0 ...
I ended up creating a special include file, with all needed "extra"
include files and doing some conditional inclusion of this
extra_include.h file ... nasty, but could not figure out another way
around. It seems some "problem" with MS compilers ...

Cesc

On 2/1/07, Athanasios Karapantelakis <athkar at kth.se> wrote:
> Hello.
>
> Are you compiling for win32, or for arm (pocket pc) ? Also, which
> version of visual studio are you using ? Regarding your error, there
> should also be an error code the vs compiler reports along with the
> message, that should be identical for all national versions. Could it be
> an issue that the compiler can't find the include files *? *(e.g.
> "Bfiles.h" requires the path declared at *Tools -> Options -> VC++
> Directories, Show directories for: Include files - otherwise an explicit
> path to the file is required)
> We will soon make an effort with Erik to get the trunk to work on
> Windows Mobile, so I think that a list outlining the problems and your
> workarounds would be very beneficial, even if it is for win32.
> *
> Regards,
>
> Athanasios
>
> Philippe Torrelli wrote:
> > Hello,
> >
> > I'm trying to compile a recent version of minisip with visual studio.
> > What I found in some places is a pattern like this
> >
> > Bfile.h:
> >
> > class A;
> > class B
> > {
> >       MRef< A *> member;
> >       .....
> > };
> >
> >
> > Cfile.cxx:
> >
> > #include "Bfile.h" <- makes the compilation fail
> > saying it's not possible to use the uncomplete type ( I don't have the
> > English message but you get the idea ).
> >
> > -----------
> >
> > For example every source file that includes - directly or not
> > -libmikey/KeyAgreement.h  and do not include libmikey/MikeyMessage.h
> > cause this problem...
> >
> > The output of visual studio makes it difficult to pinpoint the real culprit
> > because often 'Cfile' doesn't directly include A.h but a .h that includes a
> > .h that includes .. ( and so on ) and one of the .h included is a.
> >
> > And so it's difficult to figure out which class causes wich problem ...
> > So I found nothing to do but find with the compilation error output which
> > .cxx requires which types, add the 'desired' includes in the cxx.. but of
> > course it makes you 'fix' it at many places when it possibly could be fixed
> > in a fewer places..
> >
> > Are you interested in the list of such 'fixes' ?
> >
> > Regards
> >
> > Philippe Torrelli
> >
> >
> >
> > _______________________________________________
> > Minisip-devel mailing list
> > Minisip-devel at minisip.org
> > http://lists.minisip.org/mailman/listinfo/minisip-devel
> >
>
> _______________________________________________
> Minisip-devel mailing list
> Minisip-devel at minisip.org
> http://lists.minisip.org/mailman/listinfo/minisip-devel
>