> Indeed I have tried several ways to create and build projects without
> using CMake at all, and so far no luck--I still get "requires
> elevation" errors. I don't have a solution for my problem yet but it
> appears that whatever it is that is stopping me from building projects,
> CMake does not
> On 1/6/2015 7:10 PM, david.k...@engilitycorp.com wrote:
> > I have just started using a new Windows 7 host with Visual Studio
> 2010
> > Professional. When I call CMake to generate my project files, I get
> > the following output in CMakeError.log:
> Does your visual studio work without CMake? C
> What do you mean when you say "I set CMAKE_ROOT to a directory" ??
>
> That should not be necessary, no matter how you're running cmake...
>
> Is that an ENV var or a CMake variable you're setting somewhere?
CMAKE_ROOT was an ENV variable used by a script outside of CMake that (in the
more co
A small correction: the problem with "The C compiler identification is unknown"
seems to have been due to the fact that I forgot to open that particular
command window as administrator. In a new command window, run as administrator,
both -G "Visual Studio 10" and -G "Visual Studio 10 Win64" prod
I tried this with a CMakeLists file that contains only a PROJECT and
ADD_EXECUTABLE (with a single C++ source file). The only things present in the
directory before running CMake were the C++ file, CMakeLists.txt, and a batch
file that I used to run CMake. I still get the "requires elevation" er
I have just started using a new Windows 7 host with Visual Studio 2010
Professional. When I call CMake to generate my project files, I get the
following output in CMakeError.log:
==
Determining if the C compiler works failed with the following output:
Change Dir: C:/_
I am a happy camper today ...
Brad King [mailto:brad.k...@kitware.com] wrote:
> david.k...@l-3com.com wrote:
> > The command-line-and-templates alternative (as implemented in the VS 6
> > generator) had at least three major benefits.
>
> That design has been a PITA for years.
Oops. I didn't rea
> david.k...@l-3com.com wrote:
> > Brad King wrote:
> >> Perhaps the install() command is better for that.
> >
> > it adds an extra step into the procedure
>
> Just run "make install" instead of "make".
If they used make. But yes, I suppose we could have an Install "project" in
Visual Studio.
> From: Brad King [mailto:brad.k...@kitware.com]
>
> david.k...@l-3com.com wrote:
>> One thing you can do with one directory full of .exe and .dll files is
>> to copy it somewhere else—to an arbitrary directory on another computer,
>
> Perhaps the install() command is better for that.
Not if you
eally want is to control where the executable
files-emphasis on executable-are built, separately from all the other
files that I don't really need at run time.
David Karr
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Erwin Coumans
Sent: Monday, Febr
>> There are lots of questions on this CMake variable and the consensus
is DO
>> NOT USE IT. PERIOD. The implementation is basically broken for all
but the
>> most trivial case.
>
>I can tell you one thing. If the original idea of this was an attempt
>to create a CMake free build that will not work
Tyler Roscoe [mailto:ty...@cryptio.net]:
> On Thu, Jun 04, 2009 at 05:14:20PM -0400, david.k...@l-3com.com wrote:
> > I wonder if the concept of a PROJECT command in a subdirectory
> > of your top-level CMake directory is semantically sound. That is,
> > it might work sometimes but cause trouble
Randy Hancock :
> I'm getting duplicate projects included in my top-level solution
> (*.sln file). I have a cmake project() defined at the top level and in
> the test projects for convenience during development. When I use
> include_external_msproject in the subprojects it also adds the
> external
Dmytro Ovdiienko :
> Yeah. By David Cole I should merge A and B. But support right ordering
of 30
> projects... that may be not trivial.
Here is something that confuses me. At the beginning of this
discussion, you said there was a CMakeLists.txt file in the
directory: that is, you have /CMakeLis
ankit jain wrote:
> My source tree structure is:
> Main_folder
>.. Ident.c
>..folder1
>f11.c
>f12.c
> [...]
>
> Now I am able to get all the source files from all the folders. but
the
> problem is that all folder source files uses one variable v1 of this
Ident.c
> file..
>
> So th
ankit jain wrote:
> I have a folder in which there are 5 files
> folder
> a1.c
> a2.c
> a3.c
> a4.c
> a5.c
>
> Out of these from 4th and 5th iam making a library if iam working on
windows
> else with the rest three iam building one library for the folder.
> Even on windows also iam makin
Olivier Delannoy wrote:
> I would like to set include_directories on a per target basis. I
> understand that the INCLUDE_DIRECTORIES property is currently on a per
> folder basis. It is a bit of a problem as I would like to flatten my
> build and have all my targets generated in a single destinati
(You may also suffer some of the
same drawbacks, but I suspect that some "ugliness" of that sort is
inevitable when you have a generator such as yours.)
David Karr
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://
ot;
http://public.kitware.com/Bug/view.php?id=8243
This applies to every version of Visual Studio later than VS6.0,
including VS2005.
It's nice to know that there is at least some kind of workaround for
this particular aspect of the problem.
David Karr
__
make' links the compiled objects to create the executable file
"abc" because ___.
8. 'make' performs the command _ in this same
subdirectory.
9. 'make' goes on to do other things not relevant to this discussion,
and then it is done.
I think you have told us that step 6 must occur somehow, but you haven't
really told us anything about how the makefile decides to do this or
what else it does.
David Karr
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
ds to be called with _exactly_ what
command-line parameters from _exactly_ what current working directory.
I wish you success.
David Karr
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
> The issue I'm seeing, is that if libprovides library project fails
> to build, VS decides to try and build the libuses library anyway,
> and then complains that libprovides isn't there.
>
> Is this the intended behavior of VS, or did I perhaps set something
> up wrong in my CMakeLists.txt?
This
> My goal would be to have
>
> - each library in it's own directory (and a CMakeLists.txt
file
> with a add_library command)
>
> - all dependencies stored in a single file at the root level
>
> root dependency file example:
>
> target_link_libraries(mylib1 mylib2 mylib4)
>
I'm afraid this accidentally went through once already while I was in
the midst of editing it; this time it's for real.
> Suppose I have a string called "foobar". I want to be able to strip a
> specific prefix from that string and have the suffix returned to me.
> So if I wanted to strip "foo", I
o see where the OBJ files were written?
(A "find" function that worked in a command window would probably work
better, of course.)
I don't know if this is a "good" solution but it might at least be
better than the alternative mentioned in (c).
David Karr
ine points of control may require user-written template
files.) So there is a loss of functionality in transitioning from
Visual Studio 6.0 to a later Visual Studio while still using CMake.
I complained about this last month, but you finally spurred me to enter
the complaint in the CMake bug tra
> By directories I mean "Solution Folders", sorry for the confusion.
> This is a feature that allows you to add "Folders" to the solution.
> This has nothing to do with projects. You can add files to these
> solution folders. Solution folders are at the same level tree-wise
> as projects are (Direc
e was able to adapt to work within them, even when
those requirements didn't match anybody's idea of the best environment
within which to use a tool like CMake. This says something about the
power of the tool.
David Karr
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
here seems to be no other comment on the mailing list, I'll
try the issue tracker.
David Karr
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
27;t know if or when this will be one of them.
The conclusion for me is that when I write a CMakeLists.txt file for a
personal project, I never "glob" the files; but the build design of a
long-running project needs to account for who is working on it and
what procedures will work best
want, and I can probably get away with this, since the
people who run the build script will just use whatever copy of cmake.exe
I hand to them. But I would prefer to use existing CMake functionality
if it exists; and if it doesn't, I wonder if it would be worth adding
this
(placed
there by the script that calls cmake.exe); nobody configures that
project through the GUI. Maybe that's why I've never noticed any
trouble caused by deleting the cache.
There's probably a more elegant solution, but since one line in a script
apparently fixed the proble
of
> them :)
Oh darn, my long-winded (and now evidently unnecessary) reply to an
earlier posting crossed this one in the mail. Sorry about that; I hope
it doesn't waste anyone's time but mine.
David Karr
___
CMake mailing list
CMake@
UILD in return for all the other stuff. At
least it doesn't actively _prevent_ me from doing something I need to
do.
But if you really love a carefully crafted Visual Studio "solution",
with every box in every project carefully and individually filled in or
checked off or left
change in the code) one could make this happen only if
requested, for example by SET(CMAKE_DEFAULT_STARTUP_PROJECT ALL_BUILD),
which would let you choose a different default startup project if you
like.
So, the question: Does anyone want this?
David Karr
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
be very
hard for me to do without it), and to do the fancy stuff myself on top
of that. That's why I have about four or five different scripts to
invoke CMake with different sets of variables defined depending on what
kind of build I want to make.
David Karr
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
nd it's served us very well ever since, though we now have more than
1800 source code files distributed among nearly 50 libraries and
executables.
David Karr
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
37 matches
Mail list logo
