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!
Related
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
Is there a way to know when is the last time I ran a program in IntelliJ? Doesn't need to be specific, just a date will work! Thank you all.
This is not the most robust answer which could be given here, but one quick and dirty way would be to check the last modified timestamps of the target folders of each of your IntelliJ projects. Presumably, when you run a given a project in IntelliJ, it would do a build, thereby updating the target folder. The latest date you find among your projects might be the last time you ran something. Of course, if you re-ran a project which did not require a rebuild, then this method might not be completely accurate.
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 am working on some modules,actually change them.
but i don't know how i should document changes in a way that be clear and usefull for future changes.
would someone help me on this issue?
thanks.
If your project is written in one of the languages Doxygen supports, I strongly recommend using that to document your code.
By using Doxygen comments in your source code, you can easily generate documentation in a number of formats by running one command.
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 5 years ago.
Improve this question
This may seem like a kind of amorphous question, but how can you get the most of the Linux Kernel Documentation directory?
I noticed on the Linux Cross Reference that there is a DocBook directory. How do I build it, use it and is it at all useful? What other ways are there to make efficient use of this directory?
All the various make targets are documented if you try "make help" at the top of the src tree. In the case of the DocBook stuff there are multiple targets, for example try:
make htmldocs
Oh and yes it is useful stuff and will probably be the most upto date reference around. A lot of the DocBook stuff extracts documentation on the various functions straight from the kernel source tree annotations.