Hi Simon, I'm sorry for the messed up markup in the latter message. Here the same again.
On Tuesday 03 May 2011 12:57:49 Simon McQueen wrote: > Compilation with Visual Studio 2010 was not supported with OpenSplice > Community Edition 5.4.1. This is really unfortunate for us. > This is the reason your compilation failed. There are variables that > need to be set to define required include & library locations that are > not set because the version of compiler was not recognised & so the > build files don't know what to set them to. If you grep VS_HOME in the > checkout you'll see where these are. You could have a go at quick-fixing > these yourself if you like (there's only a couple & it's not rocket > science), or switch to an older version of VS, or wait a short while. > Visual Studio 2010 support is going to be released fairly soon. We will give it a try. Switching to an older version of VS would be a possibilty -- but we will consider it at last, because VS2010 is the product students can use over the MSDNAA for free. VS2008 is not supported by the MSDNAA anymore. > I don't understand how compiling without using cygwin's make and shell > interpreter would help with developing for embedded platforms. We > produce OpenSplice for a number of embedded targets with Windows as the > development platform & it all works just fine. Check the release notes > for a list of these. I recall you can sometimes used to get issues with > embedded tool chains shipping antique forks of cygwin that can cause > conflicts but we've always managed to work around these with careful > pathing. What issue do you have in mind please ? Not using the VS-compiler brings heavy ABI-problems with some precompiled libs we would like to use -- which ship without any source code freely available to compile by ourselves. So using gcc is nearly impossible if you wouldn't like to get some heart attack -- I personally don't know a solid way of using VS libs with gcc. Further the operating system on the embedded hardware has to be Windows because of the Soft-SPS kernel extension. So there is not really another possibility than using VS + Windows. Even if the majorty of us would nem con prefer Linux on the embedded system -- Windows is unfortunately still dominating the industries. > As to why we don't maintain & use Visual Studio's project files for > compilation: we have to produce OpenSplice for a great many other > platforms than just Windows. Having to duplicate effort by maintaining > one set of build files for Windows & another for other platforms is not > appealing and carries an obvious risk of divergence problems. > Microsoft's habit of changing it's file format on pretty much every new > release doesn't endear them to us either. Okay this sounds comprehensible. So I suppose we have to go the hard way and hack it by ourselves. Thank you for your patience and time! Best wishes, Knut > > On 03/05/2011 10:17, Knut Krause wrote: > > Hi, > > > > I just had a look at the OpenSplice DDS because we maybe want to use it > > in our project. Since we have to develop embedded software on Windows it > > would be nice to compile OpenSplice on windows without cygwin. Is there > > a way to get a native windows build of opensplice? > > > > This is what configure said: http://pastebin.com/ns6MVCa3 > > > > Sorry for the german output but "Kein Suchpfad für Headerdateien > > vorhanden" means "no search path for header files present". > > > > regards > > > > > > Knut > > > > > > > > _______________________________________________ > > OpenSplice DDS Developer Mailing List > > Developer@opensplice.org > > Subscribe / Unsubscribe > > http://dev.opensplice.org/mailman/listinfo/developer > > Cheers,
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ OpenSplice DDS Developer Mailing List Developer@opensplice.org Subscribe / Unsubscribe http://dev.opensplice.org/mailman/listinfo/developer
