As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have seen many projects willing to switch from autotool to cmake. I can quote VCMI, Apache QPID, and Battle for Wesnoth too.
The two main reasons I read on forums were:
cmake colour output is much prettier.
when configure.ac contains error, the build doesn’t work.
But I am not convinced by either argument. As I have a couple projects I want to distribute, I would like to have some guidelines I could follow when it comes to choosing one of the two. So, what are the differences between them? Are there things I can do with one and I can’t with the other?
EDIT:
Some arguments for automake (I haven’t verified them):
it supports "make uninstall", when cmake does not
there is no need to install anything
For some reason people seem to assume that autotools is just a "build system". It's really more than that, though. The autotools are really geared to help a project comply with distributing software under the GPL and related licenses (especially collecting the "corresponding source") and GNU project type documentation (Changelog, README, NEWS, etc). It's not that you can't do this with another build system, but you might have to take extra steps to do so. I don't know cmake or the other build tools well enough to know if there's a way to produce a tarball or something similar to autotools make dist or what gets included when you do so.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I would like to program some stuff for a LEGO NXT robot. The "API" included with the robot is quite limited, so I went on to find some alternatives. There seems to be a bunch of languages/add-ons/compilers for this task. The thing is that I don't know which one to choose, or even use. I'm on a mac with OS 10.8.
I am good with C#, Objective-C, and can work my way around C/C++ and Python. Thanks for your help.
If you like C, I suggest you try out Not eXactly C, a modified version of C for programming NXT bricks. If you prefer a version more like C, give RobotC a try. RobotC is commercial software, however.
Getting NXC up and running is as easy as installing the Bricx Command Center IDE. NXC works with the standard LEGO firmware, but it also comes with an enhanced version with bug-fixes and enhancements. RobotC provides its own IDE and firmware which you can try a 30 day trial and then purchase a license key from the RobotC website.
If you really like Python, have a look at nxt-python. It's as easy as installing a compatible driver/interface for nxt-python to communicate with the NXT brick, and then installing the latest release of the nxt-python libraries. How to do so is clearly outlines on the Installation page.
I suggest you setup BricxCC and nxt-python, and give them a try first. If NXC isn't right for you, you can grab a trial version of RobotC that you can try out for 30 days before purchasing the full version.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I facing a problem, on tracking changes made by other developers.
Note: SVN is not used for some reasons.
So, is there any better way apart from individual file comparison using kDiff. This is too tiresome for large number of files.
Such as looking for entire Project's Comparison, for projects created in Xcode.
Thanks.
You can use FileMerge that comes as part of the Xcode package. This will take two directories and compare the contents of the trees rooted at that point showing files only in one tree, that differ in the two trees, etc. For differing files you get a standard visual diff. This should give you what you need quickly and easily, we actually use it in conjunction with svn to compare branches, check merges, etc.
You can use any other SCM, it's a natural way of tracking changes ("Source Control...")
If you still want make own life harder, you can use any OS-specific tool, which can compare directories, not only separate files
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I'd like to create a flowchart/map visualization of how my project works, what is the best software available for this purpose? I'm not looking for something to do it automatically, I'd like to manually create the flowchart.
This is for a project done in Objective-C if that helps/matters.
OmniGraffle is pretty good. It even creates class diagrams from an Xcode 3.x project.
Other web applications that do this, that are not already mentioned:
draw.io, is free and uses Google Drive or Dropbox for storage (including Google Drive Realtime). I co-founded this.
Lucidchart is native JavaScript, like draw.io.
Creately and Cacoo are Flash implementations, although Cacoo are moving away from Flash.
Aside from my obvious bias, I would suggest Lucidchart or Gliffy (mentioned above).
If you (a) like gliffy and (b) want a desktop-based app that does the same thing, take a look at yEd. Supports BPMN and traditional flowcharts (as well as myriad other drawing notations). Nice and easy to use, cross-platform. Oh, and free :-)
hth.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Before you answer vi...
I'm looking to set a development environment for programmers with mainly Windows/Visual Studio background. Of course Emacs and Eclipse come to mind as IDEs, any other useful tips? thanks
I think the editor is incidental. Just read the kernel coding standards on tabs, indentation, functions vs keywords, use of braces, etc .. and it doesn't matter WHAT editor you use.
If you think your choice of editor is somehow going to improve your code or help you get into 'the zone' .. you probably aren't ready to send patches. git-send-patch exists because so many use a plethora of different editors.
If you kidnapped me and sat me down in front of any version of emacs then pointed a gun to my head and told me to code, I'd ask you to just shoot me. I have nothing against emacs, in fact I still have one of the few surviving copies on tape which I paid $50 to get a long time ago.
Use an editor that lets you focus, simple and agreeable syntax highlighting, good editing functions, sensible keyboard shortcuts .. a handy snippet gallery and the rest is up to you.
Or, will a Chevy improve your driving over a Toyota (had to put a straw man argument in there somewhere, after all, this is debating Linux development)
In the spirit of that, I'm now going to re-tag your question.
Well, if you are doing Linux Kernel work, perhaps you will be interested in Mr Torvalds opinion of emacs...
According to the Linus FAQ he uses MicroEmacs. :-)
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm not talking about bug tracking software (like Bugzilla or Jira). I'm looking for something that:
Stores test specifications in text format
Combines test specs into test coverage scenarios
Keeps track of the progress through testing scenarios
Links test specs with bug reports stored in Bugzilla
Generates progress reports
Is centrally managed on its own (i.e. is not a hack/extension on top of something else)
TestLink is a pretty nice open source test tracking tool with the features you need, and is still under active development. Take a look at http://testlink.org/
I haven't used this (yet), but Testopia seems to meet all your requirements, especially the one about Bugzilla.
I'm biased since I'm the primary author, but I think Cuanto is pretty good. It allows you to track historical results for multiple test projects and you can store your analysis with the test results.
RTH is another open source test management tool
I have personally used Trac (http://trac.edgewall.org/) which combines a simple issue tracker with Wiki functionality. Solved the need I had on my project.
A while back I briefly looked at the free version of QaTraq. Although I left the team I was considering it for before we every got very far with the project, it was the frontrunner of the options I looked at at the time.
It's got quite a nice interface, and what seemed to me to be a very sensible test planning structure. I think one of the big downsides was the the open source version didn't have table support in the WYSIWYG test case editor - Not a showstopper, and could be fixed with a little development effort or by spending some money on the professional version.