Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I am a bit confused about CMake workload, so in a project with my sources I add a CMakeLists.txt, and in a build dir i just create the CMake build project which only will be used to build, so that i only edit in the location where originally are my sources.
Yes. This is called "out of source builds".
It has multiple advantages over the old style of having a "build" subdirectory or putting the object files directly next to your source and header files.
Most obvious advantage is that you can guarantee that everything is rebuild when you delete the build directory. In our build automatisation file we make the source tree readonly to guarantee a clean build without accidental checkins of build fragments.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 18 days ago.
Improve this question
I would like to know if there is any guidance the question below, be it from the official CMake documentation, "industry-standard" or anything the like:
Should a program be executable from the build directory after just the CMake build step?
In other words: If I build my program with CMake and I want to run it. Should I be able to run/use it directly out of the build directory or do a lot of programs only work after an install step for example?
In other, other words: Is the effort to make my program runnable in the build directory a good idea or just unnecessary? What do other programs do? Is there any guidance on this particular question?
In my research I found that it probably should be that way, but I found no actual source for this, that would answer me this. Especially not with any explanation or justification.
Any help is appreciated. Thanks!
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
To Zerobrane users, since this is not a question on lua :
I use Zerobrane for editing lua programs that are to be used with LuaLatex. Very nice !
I make all tests there before using the developments in LuaLatex. So, at the beginning, the programs are run there. I need to tidy up this part, on ZeroBrane, by making files hierarchical, with a master file and slave files around.
Once again, it is a question about ZeroBrane, not about how I use the file within LuaLatex (I know enough about doFile, luaexec and co)
Does this exist ?
I saw PaulK passing by, if he could drop a line, it would be appreciated ...
An "include mechanism" as you call it is usually a language feature, not some feature of an IDE.
Lua provides various functions for running code from other files.
dofile, load, loadfile, require, ...
The most convenient and common is require which will find a file by its name in a given set of directories and execute its contents.
Read this:
https://www.lua.org/manual/5.3/manual.html#6.3
https://www.lua.org/pil/8.1.html
https://www.tutorialspoint.com/lua/lua_modules.htm
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Is it normal to include the source for a testing framework in the tested application's repository.
For example, a C++ application tested with googletest. Does googletest code go in my repo? If so how do I handle building. Do I have my makefile call googletest's makefile?
Alternatively, should I ask the end user to provide an environment variable pointing to googletest if they want to run the tests?
Typically all your tests will be in a separate repository, I know for us we have all of our integration tests in a different repository but keep unit tests local.
Do you really want your clients to see all your test cases? Do the tests really need to be run on client machines? These are questions you have to ask yourself. Then you will have your answer
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I need to setup the Team Coding Environment i.e. Two or more people, over the local network can code together on a project (PHP coding). How should I get started...
You really don't want to people to work on the same files.
Let both of them work on their own files (locally or on separate folders on a server) and have them use a VCS such as Git. This ensures conflicting modifications do not simply overwrite someone else's code but have to be properly resolved.
You should consider using any kind of SCM (Git, SVN ...) and an IDE which support this SCM (netbeans, eclipse).
Git and Github seems to be the trend of the moment. You should give it a look
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I have a maven project that has both code and documentation (pdf files). When I create a release of my software, I'd like to package the jar file and the documentation for the user. Is there a "correct" way to do this in maven? Should I have a multiple modules - one for the code (it's a small project, so the code is a single module right now) and one for the documentation? One module for each documentation pdf? Or some other way to package it in a single project? Any help with this would be appreciated.
thanks,
Jeff
When I create a release of my software, I'd like to package the jar file and the documentation for the user. Is there a "correct" way to do this in maven?
I would use the Assembly Plugin to create a zip and/or tar.gz distribution of the project containing both the jar and the various PDFs files.
Should I have a multiple modules - one for the code (it's a small project, so the code is a single module right now) and one for the documentation? One module for each documentation pdf? Or some other way to package it in a single project?
I don't really see the need, I'd keep everything in a single module and put the PDF in src/main/doc or something like that.
Take a look at the following post: Creating Documentation With Maven, It could very well answer your question.