[Insight-developers] itkBasicArchitectureTest: VC++

[chenting]

I think I have the same problem, the only difference is I am using CC7.3 on
unix, it seems there is something wrong with the itkBasicArchitectureTest. My
result is the following:
.....
cd Testing/Code/Common; make - all
CC  -LANG:std -ptused -no_prelink   -I.
-I/Insight/Code/Insight3DParty/vxl  -I/Insight  -I/Insight/Code/Common
-I/Insight/Code/Insight3DParty/vxl  -o itkBasicArchitectureTest
-L/Insight/Code/Common  -lITKCommon  \
  -L/Insight/Code/Insight3DParty/vxl -lITKNumerics -lm
ld32: WARNING 84 : /Insight/Code/Common/libITKCommon.a is not used for
resolving any symbol.
ld32: WARNING 84 : /Insight/Code/Insight3DParty/vxl/libITKNumerics.a is not
used for resolving any symbol.
ld32: WARNING 84 : /usr/lib32/mips3/libm.so is not used for resolving any
symbol.
ld32: ERROR       33 : Unresolved text symbol "main" -- 1st referenced by
/usr/lib32/mips3/crtl.o.
            use linker option -v to see when and which objects, archives and
dsos are loaded.
.....

So where might be the problem?
I use CC7.3 on a SGI machine with irix6.5
thanks!
ting





Bill Hoffman wrote:

> 1.  It is possible that things are mixed up a bit.  The way I created
> this, was to use the wizard then copy the files.
>
> 2.  I have not tested the Release version.  I think most are using the
> Debug only right now.
>
> 3. I am getting console applications from the exe files.  Is that a release
> /debug problem as well?
>
> 4. About the MIDL, that is the idl compiler for COM/ActiveX stuff.  I think
> it is standard, but we are not using it.  Again, this came from a
> wizard generated file.
>
> >Hi,
> >
> >I just updated and re-compiled (VC++ 6.0) from scratch, and got the some
> >link errors that I've had for awhile....see end of email.
> >
> >0) Is anyone else using VC++ 6.0 right now?
> >
> >1) itkBasicArchitecture and other exe's are set to compile (debug
> >version - in EXEHeader.dsptemplate, you set /MD in debug session) as a
> >multithreaded dll and the release version is set to compile as single
> >threaded (non-dll).   If I change to /MDd (multithread dll with debug)
> >for debug and /MD (multithread dll) for release, I don't get link
> >errors. BUT, I don't understand why these should be compiled as dlls?
> >This makes no sense to me - can anyone enlighten me?  I don't want to
> >change things I don't understand.   This is unlike any other VC++
> >project I have used/developed.  Perhaps it is because of (2) below...
> >
> >2) Things are set to compile as windows applications instead of console
> >applications.   We find better compatibility (most importantly, we are
> >able to use cout's) if we compile as console applications.  Would you
> >find this change agreable?
> >
> >3)  You use the MIDL compiler.   This is one way your project files
> >differ from mine, and my version of MSDN (July 1999) doesn't have any
> >info on MIDL.   Is it important?
>
> _______________________________________________
> Insight-developers mailing list
> Insight-developers at public.kitware.com
> http://public.kitware.com/mailman/listinfo/insight-developers