[omniORB] FW: VC++ 6.0 makes error C1010 when the skeletton is
added to the project
Pánczél Levente
Levente.Panczel at compuworx.hu
Wed Sep 24 17:36:14 BST 2003
-----Original Message-----
From: Pánczél Levente
Sent: Wednesday, September 24, 2003 4:20 PM
To: 'omniORB-list-request at omniorb-support.com'
Subject: VC++ 6.0 makes error C1010 when the skeletton is added to the project
Hello!
These are my first steps using OmniORB: I'm looking for a suitable ORB for my company.
Though I might have misread things, I've made awful experiences with OmniORB: I can't get anything to work.
My main problem now is, that the Visual C++ 6.0 project attached does not compile. To be more exact, I don't even think it passes preprocessing, though I never wrote a #.
Symptoms are the following: I'm writing the GUI Client to a very simple component (I'm using MFC for the GUI). I have the binary distribution of OmniORB 4.2 "installed", and set up everything just as described in README.Win32. Without the skeleton (calc_sk.c) in the project: everything is compiling, only the linker is worried about the missing symbols located in the skel. So I include the calc_sk.c (I changed the file extension using appropriate parameters to omniidl so that programs recognize it as a C/C++ file). And then I always get the error C1010 on this file: unexpected end of file while looking for precompiled header directive. Well this sounded too unintelligible for me to track down the problem, so I commented all the contents of calc_sk.c, and most surprisingly got the same fatal error again. Actually if I add any file to the source files, it never reaches compilation stage (even a blank, or a syntactically invalid C/C++ file generates the same error, and no others; that's why I think it is raised by the preprocessor). I can build the example programs fine, but I can't build my MFC-based client. I find this is horrible. Please tell me, if you know the solution!
(
Another problem I could not solve involves Linux. On another PC I'm using a Suse Linux 8.0 distribution. I built OmniORB for it using configure. I can build all the examples, but cannot compile outside of the build-tree of OmniORB, 'cos I can't figure the external dependencies and required #define-s out. README wrote that the makefiles in the example source directories should give me an idea of what to do, but they don't: they don't work without the top-level makefile configure, wich is too large and unintelligible for me. I found a shell-script obuildtree (which can make a build-tree for me, I hope; but I still don't get how to link my own makefiles to it).
)
Thanks for you patience:
Pánczél Levente
Levente.Panczel at compuworx.hu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20030924/3c812de0/attachment.htm
More information about the omniORB-list
mailing list