Compiler support - Was: A good looking idea and project but need help to get feeling how it works

[Klaim - Joël Lamotte]

On Fri, Feb 15, 2013 at 5:05 AM, Joonhwan Lee <joonhw...@gmail.com> wrote:

PS: What exactly you want to achieve w/ or w/o a ceratin tool could be shared with the member of this group and possibly we can talk about it.

For compiler stuffs, I'm only concerned with three things:

 - Visual Studio compiler and GCC or Clang don't have exactly the same level of conformance to the C++ standard, even if they are pretty close - it's easy to write C++ code in VS which cannot compile on other compilers, in particular in template code;

 - VS is really late on the C++11 features, which I find to be a big handicap: I have another big project I'm working on where I had several part of code which would have been simple to write with variadic templates for example, but had to hack my way around the lack of feature; 

 - Portability: writing with only one compiler for all the targets simplify things a lot.

However, as you mentionned, VS is clearly the best debugger for Windows development.
And it's the first target platform so far.

So as I said, I will not put energy in portability for now and use VS(10 for now, 12 soon) as before, until we reach the point we need the Mac and Linux versions of AOS Designer.

Joel Lamotte

[Joonhwan Lee]

Frankly speaking, I wish I could run AOS in my mac at home(I've not tried to build AOS in my box though. will do that after some kind of very initial pro to version).

 

I think I can consistenly check AOS for mac while you're working/focusing on Windows.

Joon

2013/2/15 Klaim - Joël Lamotte <mjk...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "Art Of Sequence Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aos-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
이준환
www.joonhwan.org

[Klaim - Joël Lamotte]

On Fri, Feb 15, 2013 at 11:19 PM, Joonhwan Lee <joonhw...@gmail.com> wrote:

Frankly speaking, I wish I could run AOS in my mac at home(I've not tried to build AOS in my box though. will do that after some kind of very initial pro to version).

I'm guessing you mean AOS Designer here? Which imply AOSCPP that is a dependency.

 

I think I can consistenly check AOS for mac while you're working/focusing on Windows.

That would be awesome! I don't have access to a Mac these days.

Just fixing the CMake files so that you can use XCode would be very helpful! 

For now, just use the aos repository (in bitbucket currently) to try things and I'll notify here when I finish fixing the CMakes for the splitted repos.

Joel Lamotte

[Joonhwan Lee]

Currently still hairy in my brain. I'll do that as soon as your new git repo is prepared.

2013. 2. 16., 오전 7:30, Klaim - Joël Lamotte <mjk...@gmail.com> 작성:

[Klaim - Joël Lamotte]

On Friday, February 15, 2013 11:59:47 PM UTC+1, Joonhwan Lee wrote:

Currently still hairy in my brain. I'll do that as soon as your new git repo is prepared.

If you still find you have some hard time to figure out how the projects work, please feel free to ask me what you don't understand.

(Maybe in another thread, or through private emails if you want)

I think that once I finish to explain how AOSL works, it will be easier to explain how AOS Designer should work too.

To get back to the topic of compilers, I manage to compile AOS Designer with a VC11 64Bit binary of Qt5.0.2 which is available there: http://releases.qt-project.org/digia/5.0.2/latest_successful/2013-02-28-439/
However, I couldn't link with CodeSynthesis XSD. The CMake script for finding XSD is too simplist, it don't take into account the 64bit binaries which are provided with the XSD build.

The CMake script is a hack I've set, using a previously written script. I'm not happy with it and will see if I can fix that, but I'm not very familiar with writing find_package scripts for CMake.

I will see with XSD developers if there is work for providing a better find package script.

I took the time to try to use QtCreator (from the installer from the link) which should have worked. However, it exposes CMake error which I don't understand so far.

I guess for now, until I fix the XSD script, I'm still forced to use VS2010 with Qt5.

Joel Lamotte

[Klaim - Joël Lamotte]

On Fri, Mar 1, 2013 at 4:22 PM, Klaim - Joël Lamotte <mjk...@gmail.com> wrote:

The CMake script for finding XSD is too simplist, it don't take into account the 64bit binaries which are provided with the XSD build.

The CMake script is a hack I've set, using a previously written script. I'm not happy with it and will see if I can fix that, but I'm not very familiar with writing find_package scripts for CMake.

Actually it's the Xerces C++ CMake find script which is wrong.

I'm trying to fix it now.

Joel Lamotte

[Klaim - Joël Lamotte]

On Fri, Mar 1, 2013 at 6:23 PM, Klaim - Joël Lamotte <mjk...@gmail.com> wrote:

Actually it's the Xerces C++ CMake find script which is wrong.

I'm trying to fix it now.

I fixed it but commited only yesterday.

So for now, I'll be using the 64bit version of Qt to be able to work with VS2012 to benefit from several improvements.

Joohwan, for now I will not use features that are not in 2010 so it should still compile with 2010. However, I will use qt5 from now.

Also, I will very soon delete the utilcpp subproject and replace the logging system it provided by Boost.Log.

Boost.Log is excellent but will not be in the normal boost distribution until next release (next month I think).

So you just have to get the sources of  Boost.Log V2 from sourceforge, then put it in your boost code and compile it.

I filed a bug to Qt so that they provide a 32bit SDK for vs2012. If they don't I'll have to compile one mysefl at some point or

find someone who did.

Joel Lamotte