Re: [certi-dev] Supported platforms

[Jan-Patrick Osterloh]

Hi Eric,

Am 4. September 2013 09:48:15 schrieb Eric Noulard <address@hidden>:
> 2013/9/3 Jan-Patrick Osterloh <address@hidden>:
> > Hi,
> >
> > --- Quoted from Eric Noulard (Date: 03.09.2013 09:48): ---
> >> The current dashboard is using free hosting which limits the number of
> >> possible submission, we may switch to unlimited submission dashboard.
> >> If someone is submitting a dashboard entry we try to keep it "green"
> >> between two CERTI release.
> > Speaking about the dashboard: I have currently no idea, why the mingw
> > nightly build fails. Everything is build, but ctest cannot find the
> > binaries. I even added the build path to the PATH environment variable.
> > I would expect, that ctest looks in the "${CTEST_BINARY_DIRECTORY}" for
> > the executables, but obviously it doesnt. Any idea?
>
> No. I though ctest should use absolute path.

My CTEST_BINARY_DIRECTORY is relative, but I can try an absolute one.


> Does it occur when you run ctest at the root of the build tree of a
> "manual" source+build tree?
> Could you try:
>
> $ cd /to/builddir
> $ ctest -VV -R LibHLAClocks
>
> the 'extra verbos' (-VV) mode of ctest shall give you more informations.

I'm currently on a business trip, I will check this as soon as I'm back 
next week.

> Side-question: do you know how to calm down the
> "warning: auto-importing has been activated without
> --enable-auto-import specified on the command line"
> should we really activate this option?
>
> Is this new with some recent MinGW version ?

No, this is not new, I have the same warning as soon as I compile with g++. 
To get rid of it, a simple "-enable-auto-import" in the linking part is 
enougth.


Bye
JPO