500 http://raspbian.raspberrypi.org/raspbian stretch/main armhf Packages
100 /var/lib/dpkg/status
(possibly your /etc/apt/sources* setup does not have
working/updated info for stretch/main repo?)
HTH,
Andreas Mohr
--
Das "S" in "IoT" steht für "Securi
Windows 7 with Visual Studio
> generators and other projects are also generated without errors on the same
> Linux machine.
>
> Does anyone knows the source of that error?
Rimshot idea:
Quite possibly someone did a
project(foo C C++)
rather than using the (IIRC - no docs here
configuration variables/mechanisms
to generically switch this naming pattern though)
- it's extremely compiler-specific (read: not environment-generic)
So, I would recommend going the "improve external tool support" route instead
(or resort to figuring out CMake config mechanisms
ich one might want to discover
and fix,
in order to have the need for any manual tweaking (in all sufficiently standard
cases)
avoided in all future deployments...
Thanks,
Andreas Mohr
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.or
ication of IDL files etc.
(but perhaps it's wise to choose a language identifier
other than a plain "IDL", since CMake might choose
to provide generic IDL support on its own eventually).
HTH (got milk?),
Andreas Mohr
--
Powered by www.kitware.com
Please keep messages on-topic
editing on aptosid live, Iceweasel 10.0.12 (whoops).
Hmm?
Thanks,
Andreas Mohr
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
informa
t;... (*** SIGH ***).
get_property(test_location_ TARGET "${_target}" PROPERTY LOCATION)
set(testexe_ "${test_location_}")
add_test("${testname_}" "${testexe_}")
endfunction(_ctest_add_test_sanitized _target)
endif(cmake_add_test_command_signature_
act since at top level both targets will end up known,
one could even skip having to define some new utility functions
for that purpose, by simply directly adding link instructions there -
but that could arguably be quite a bit less clean
than providing internal helper functions to abstract certain int
nd then these would simply check whether a marker
is available (perhaps marker file stored on a temp fs).
So, IOW, the installer option would only need to have the capability
of creating those marker signals somehow (in case the user selected the
corresponding option),
then the unconditionally execu
quot;exact_same_cmake_line_content_as_executed")
(or, IOW,
message(FATAL_ERROR "target_link_libraries(${Target} ${SQLITE3_LIBRARIES})")
)
whenever needing to analyze why things fail.
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kit
t I'm sure some people would say "always use c)".
HTH - anything else?
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.
Make library,
resorting to Find* (Module mode) rather than Config mode seems obvious.
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cm
nt forums
on the internet discussed this, and AFAIK the suggested workaround
was to do things via target dependency chaining instead
(i.e. implicit "generated file" hookup does not work,
thus one needs an explicit *target* for that conversion handling,
and then explicitly let something el
to wrap it into a new policy
setting since some build environments might have hard expectations about
that behaviour. OTOH you seem to indicate it's specific to certain
generators only, thus behaviour over various generator types *is* varied already
thus people should have known to deal prop
rts
within these expressions, which would be the <...> parts ( etc.).
For details, see all the Platform setup modules within CMake's
pre-installed modules, i.e. INSTALL_PREFIX/share/cmake-VER/Modules/Platform/ ,
since *this* is where the game gets played, i.e. where all the magic
happens, t
/all] Error 2
> make: *** [all] Error 2
A frequent CMake pattern is to have one CMakeLists.txt per each files
directory (to always have processing symmetrically going from foo_SOURCE_DIR to
foo_BINARY_DIR, such as configure_file() etc.).
Thus without even analyzing the problem (apologies!),
x27;t
>output them. Cmake may be logging this stuff too (to send to cdash for
>example) so this is kind of a responsible choice.
Indeed, that possibly gets decided via the controlling terminal's features.
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware ope
g. parallelization (make -jX) configuration
through it
as well, so it might be useful to devise a standard parameterization
mechanism for --build to support *any* such attributes, in a generalized form.
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://
y I found that Macports even default-includes
a Win32 wxWidgets cross compile package,
so there might easily be enough infrastructure support for Qt cross compile
to make it a worthwhile modus operandi.
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.ki
On Tue, Apr 30, 2013 at 09:44:35PM +0200, Alexander Neundorf wrote:
> On Tuesday 30 April 2013, Andreas Mohr wrote:
> > Consider /opt/local/lib/cmake/OpenCVConfig-version.cmake
> > Visit /opt/local/lib/cmake/OpenCVConfig-version.cmake/
> > CheckDirectory (dir /opt/local/l
ild package (OpenCV is fully
CMake-enabled!).
And, I have to add that, this should especially be the case in light of
the uninformedness of many users (and, after all, a system should
ideally just work, intuitively... but that's the usual rather unattainable
goal).
(sorry! :)
(oh well,
ppen to want to
have a look at this case... (some sizeable infrastructure extension
probably required)
Thanks,
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMak
it.
There's nothing to add to that.
> David Cole
> (still sorta reachable via dlrd...@aol.com)
Good luck!
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check t
to figure out the changed/added parts,
or figure them out manually (obviously less reliable),
or send both files to someone who can analyze it this way.
Thanks for the report!
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensou
e would offer precisely tailored packages via each
version of these systems, but that's a large overhead
that's probably a pipe dream in many situations.
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.
ted specifically-pathed
*temporary* project files, CMAKE_USE_RELATIVE_PATHS
(and possibly avoidance of manual reference to ${CMAKE_PROGRAM} expressions,
to try to even avoid any CMake dependency at all) would be very useful.
> Does anyone have succeeded with relatives path in CMake ?
On my r
g_yes_no}=yes
set cfg_build_debug_enabled_int=1
set cfg_build_release_yes_no=no
set cfg_build_release_enabled_int=0
set ${var_name_debrel_string_lower}=debug
goto cfg_build_flags_done
:cfg_build_flags_done
"
)
set(${_out_debug_flag_content} "${sbuild_configure_batch_debug_flag_content}"
PAR
y license acknowledgement step.
IOW, this strongly hints at RPM install step being the wrong place
to do such things.
HTH,
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check
ng (outdated) signature (variant) of a certain CTest setup function.
> SET(CTEST_BUILD_NAME "Linux_Standart_Valgrind")
"Standard", *pretty please* ;)
> #set cMake command to be used
> SET(CTEST_CMAKE_COMMAND "\"${CMAKE_EXECUTABLE_NAME}\"")
Hmm, does this
s transmission channels,
and then obviously strongly attempting to end up with the same set
of fully qualified data payload at the sink side
as was put in at the source side).
So perhaps it's the prior layer which is broken
and thus should do things differently
(i.e., avoid passing a backslash-esca
quot;)
Or another trick might be to mark all quote positions within the string
with a different marker char and then use some regex replace on that string
to replace those with quotes.
Perhaps the result string then ends up more precise (read: successful)
than the previous fruitless attem
ried
> things like declaring INCLUDE_DIRECTORIES(/opt/local/include) and
BTW CMake >= 2.8.8 (AFAIR) now finally has a target-specific (i.e.
non-directory scope) INCLUDE_DIRECTORIES property for specifying these
things.
HTH,
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware open-so
- grab all required elements from the GLOBAL properties set by the sub
directory code and configure your local targets with these
[plus, for possibly target-specific configuration done by the Config file,
provide a dummy victim target to gather these values from]
This mechanism is so stu
space issues here.
So it's at least *better* than it used to be, but there might be hidden
niceties lurking
(and this is what the dashboard test result likely hints at).
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/o
easily re-build a CMake of your own that has it enabled. Simply turn on the
> advanced cache option CMAKE_ENABLE_NINJA when configuring CMake.
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep
ot) enable wx2.4 build compat config flag
(and thus end up with incompatible vtable ABI issues).
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ a
ainful way,
whereas many major SCM tools have quite flexible d2u handling builtin...
(had to put this tag here for my admittedly less specific reply)
BTW, I currently have an updated version of the "community-maintained"
(see related tracker item) PCH support Module within my vcproj2c
be
extended to document these potential include pre-conditions.
The best way to verify define existence would obviously be a more _manual_
compile setup
of a dummy source plus header include.
Andreas Mohr
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitwa
tent-Type: text/plain; charset="ISO-8859-1"
>
> Andreas Mohr wrote:
> > I'd think that Debug/Release isn't all that matters -
> > what discussions all too conveniently leave out (possibly even the KDE
> > Wiki-side target config discussion!) is pl
latform cfg from HOST-side rather than TARGET-side attributes]
Thus spake someone who still hasn't found the time to implement
at least a semi-usable/-supported (static) CMake way
of platform configuration type dependent switching in his V2C converter... :-P
(1 year old bug report an
e, apt-get or some such).
dpkg will not install missing dependencies.
Probably the best thing to do is to push the package
to some APT pool server out there (possibly even your own),
then have a user add that URL to /etc/apt/sources.list.d/
and install everything automatically via apt-get
Andre
27;m currently not
entirely sure, but IMHO using configure_file() should provide exactly that.
I.e. configure_file() from original file to the destination file
which you then file(STRINGS...), and it should trigger re-configure
whenever the original file changed.
Andreas Mohr
--
Power
es a
> binary for windows). You can see the command and the error below.
>
> cmake -DCMAKE_INSTALL_PREFIX=~/local/install/bpp/windows -
> CMAKE_CXX_COMPILER=/usr/local/i386-mingw32-4.3.0/bin/i386-mingw32-g++
Would possibly be useful to specify the second variable via -D, too :)
HTH,
on!!)
install code. Required dependencies' install() handling
should predominantly be processed _first_
and _then_ any custom code of the parent config should be executed.
While a (parent) cmake_install.cmake should be configurable for insertion
of custom code either at the beginning or end
t need more stability and could thus
keep subscribing to "experimental", whereas "master" currently is (too?) old.
If someone would like to create CMakeLists with it or use .vcproj
in their build, then simply ponder making use of the converter
(and possibly let me know of any is
doing something like:
[ ... run build stuff ... ]
pseudo_random=$(date +%s) # UNIX Epoch seconds (don't use %N nanoseconds since
it's not portable, plus it's overkill)
run_tests=$((${pseudo_random} % 42)) # modulo, obviously
if [ ${run_tests} -eq 0 ]; then
echo "INFO: running uni
CMake configure run build tree info is lost, and things
have to be rerun (best done via a manual "${CMAKE_COMMAND} ."),
as clearly opposed to what happens in the Makefile case,
where the generated build environment is still left alive
and you can simply restart build via make.
Andreas Mo
does work properly with Unix
Makefiles
- actual execution _ordering_ is supposed to be done by specification of
corresponding
target dependencies, and this is what fails with Ninja generator).
Ninja generator - blazingly fast execution due to guillotineing some 72.13% of
all dependen
On Tue, Sep 13, 2011 at 03:33:01PM +0200, Alexander Neundorf wrote:
> On Wednesday, September 07, 2011 11:12:55 AM Andreas Mohr wrote:
> > Depending on actual implementation of CMake (whether it has some caching
> > logic or not), this might be woefully inefficient,
> &g
endless amount of
individually caching layers, but in this case it could make a difference...
Thanks,
Andreas Mohr
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep
then include(libxxxConfig.cmake)
(more or less specifically or implicitly pathed)
(or alternatively include a Use file which _both_ includes Config file
_and_ then activates these include paths for the local project)
Or, more specifically, Z would s
e added/changed for a more suitable
implementation?
- add these things to a new bug# for implementation
Done Deal?
Thanks,
Andreas Mohr
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
ed quite well, though
(all things pushed into build-time actions as much as possible).
OTOH your setup may very well be orders of magnitude bigger than mine
(perhaps many more small targets), which could explain the difference.
Andreas Mohr
___
Pow
ackaging (non-NSIS).
On UNIX restricting CPack generator to TGZ or restricting the COMPONENT:s to
be installed helps.
--> you should try aggressively to figure out some methods (via
option()s or some such) to reduce the amount of packaging activity being
done for test purposes.
Andreas Mohr
__
On Thu, Dec 23, 2010 at 09:11:53AM +, Mike McQuaid wrote:
> On 22 December 2010 22:24, Andreas Mohr wrote:
> > To put it simply, I was just not happy the entire time while
> > trying to implement this and not finding any satisfying (well-crafted)
> > solution,
> >
Hopefully my story will enable people to see where there are problems
and how to approach any potential solutions.
I have to say that so far I'm quite happy with the sufficiently large
infrastructure that I was able to create, it's just that many areas
feel wanting (the entire BundleUtili
potential solution might actually turn out to be
generator-specific (e.g. Makefile). :-P
I'm afraid since CPack is likely executing a generated CMake
environment, detection is difficult or even impossible.
Several varied Google searches didn't turn up much.
Andreas Mohr
___
Makefile or Project.
"some sorcecode" == 2MLOC on my side of the fence. It's working ok so far.
Andreas Mohr
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
P
" to CMakeFiles.
(not that anyone unclever enough would ever happen to read these files
before getting rid of them in sub-seconds, but...)
> The fact that it can't create a directory alone makes cmake freak out almost
> immediately.
Interesting vari
orgot to set some CPack RPM path-/file-related variable,
causing the base path to be incorrect, but I currently don't remember which one.
This is a rather stupid indirect error case with a very confusing error
result and thus should be improved properly in CPack if possible.
I can send y
dvalid on a DTD (as hopefully
published for VS2005/08/10 etc.).
Unless that's still not precise enough for full validation of all
content.
Obviously this should best be made a mandatory post-build step prior to release.
HTH,
Andreas Mohr
___
Powe
how during target building
or some such.
This is quite certainly not the most direct (nor elegant!) way
to force a reconfiguration (any ideas how to force it directly?),
but in some situations such a reconfiguration might help.
Andreas Mohr
___
Power
bly are ExternalProject_Add()
or Imported Targets.
Or, another way to achieve reduced build times might be things like
distcc, icecc, ccache.
On my side, I'm currently working on a flat CMake project space (and as said
above this is working sufficiently well),
however I might eventually
ind
a way to have my vcproj2cmake rebuild step cleanly registered _right
before_ the cmake_check_build_system step.
Any clever ideas?
Currently using 2.6.4 mostly, but that's certainly not a limiting issue.
Thanks,
Andreas Mohr
___
Powered by
\VNI\CTT5.0\include\IA32" /fpe:3 /nologo ${COMPILE_DEFINITIONS}"
>
> Invalid escape sequence \V
Likely someone forgot to use a VERBATIM somewhere.
Andreas Mohr
___
Powered by www.kitware.com
Visit other Kitware open-source projec
ull
of rather very internal CMake experience (Google searches in the couple
hundreds, vcproj2cmake adaptation of a _large_ project etc.).
Suggestion for the sake of world peace: I'll submit a patch for that man
page, ok? :)
Andreas Mohr
___
Powered by www
erhaps you won't need these).
OTOH your issue might be the split between Fortran and C++ components,
in which case even CMAKE_LINKER might fail to help in all cases
(in that case perhaps there's a target-specific property to set
which defines the linker to use for the target).
HT
dle multi-configuration generators
in a much better way (though I still haven't tried it yet ;).
Andreas Mohr
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep
UGIN_DIR_BUILD could probably be figured out using things such as
${LIBRARY_OUTPUT_PATH} or ${CMAKE_BINARY_DIR}/...
Andreas Mohr
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensourc
Hi,
On Mon, Jun 14, 2010 at 05:00:47PM +0200, Andreas Mohr wrote:
> On Mon, Jun 14, 2010 at 09:54:58AM -0400, Bill Hoffman wrote:
> > To be compatible with CMake, I would say a BSD license would be the
> > best. gitorious might be a good starting place. We tried the converter
On Tue, Jun 15, 2010 at 11:10:37AM +0200, Jesper Eskilson wrote:
> On 06/14/2010 05:00 PM, Andreas Mohr wrote:
>
>> Frankly the entire distinction between CMAKE_CONFIGURATION_TYPES
>> and CMAKE_BUILD_TYPE remains one of the more confusing things,
>> as can be witnessed in s
I'll get that issue resolved soon - need to do some .vcproj
conversion testing anyway.
BSD license due to CMake using BSD license is a good argument,
not sure yet whether we'll buy it though ;)
Note to grandparent poster: putting into Wiki seems a bit weak
from a version c
#x27;m always open to suggestions on how to add one's implementation to
the script ;)
Andreas Mohr
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages o
s once delivered to customers.
Thus licensing as GPL seems out of the question (though not entirely sure
how a special "script project" would be affected by GPL regulations),
and LGPL seems to be the goal. Rrrright!?
Both scripts are attached.
Any comments or ideas?
Thank you
configuration
is expected currently.
Otherwise you will keep having to add exceptions to the CMake config in
the sub project whenever the parent project name / specifics change.
HTH,
Andreas Mohr
___
Powered by www.kitware.com
Visit other Kitware open-so
I guess, thus any projects added in sub directories in the meantime
shouldn't manage to influence evaluation of the parent project's name.
HTH,
Andreas Mohr
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http:/
76 matches
Mail list logo
