What have you tried? » Matt Legend Gemmell. If you’re a developer and you’re about to ask another developer a technical question (on a forum, via email, on a chat channel, or in person), you’d better be ready to answer the question “What have you tried?”
This of course isn’t specific to software developers, but that’s my field and it’s thus the area in which I’m most familiar with the issue which motivated me to write this. I’m (sadly) quite sure that it applies to your own industry too, whatever that might be. The thing is, there’s a disease in the software development world; a sort of sickness.
It’s an unusual sickness in that it’s often not something you acquire once you actually join the industry (like greying hair, caffeine addiction and an ulcer), but rather it’s something that new recruits already have when they arrive. Now, a quick clarification before I continue: when I say “new recruits”, I don’t just mean graduates and other young people. The illness, of course, is a flawed approach to solving problems. But wait. CI Feature Matrix. Hudson CI. Redmine - Overview. JIRA bug tracker. GreenHopper project management. Crucible code review tool. Bamboo CI.
Play! Framework. Java. Perl. SWIG on Windows - Getting Started. This chapter describes SWIG usage on Microsoft Windows.
Installing SWIG and running the examples is covered as well as building the SWIG executable. Usage within the Unix like environments MinGW and Cygwin is also detailed. 3.1 Installation on Windows SWIG does not come with the usual Windows type installation program, however it is quite easy to get started. The main steps are: Download the swigwin zip package from the SWIG website and unzip into a directory. 3.1.1 Windows Executable The swigwin distribution contains the SWIG Windows executable, swig.exe, which will run on 32 bit versions of Windows, ie Windows 95/98/ME/NT/2000/XP. 3.2 SWIG Windows Examples Using Microsoft Visual C++ is the most common approach to compiling and linking SWIG's output.
More information on each of the examples is available with the examples distributed with SWIG (Examples/index.html). 3.2.1 Instructions for using the Examples with Visual Studio. Slashdot Stories (10)
Nagios plug-in development guidelines. Development platform requirements Nagios Plugins are developed to the GNU standard, so any OS which is supported by GNU should run the plugins.
While the requirements for compiling the Nagios Plugins release are very basic, developing from the Git repository requires additional software to be installed. These are the minimum levels of software required: GNU make 3.79 GNU automake 1.9.2 GNU autoconf 2.59 GNU m4 1.4.2 GNU libtool 1.5 To compile from Git, after you have cloned the repository, run: tools/setup . Plugin Output for Nagios You should always print something to STDOUT that tells if the service is working or why it is failing. As Nagios does not capture stderr output, you should only output to STDOUT and not print to STDERR. Print only one line of text Starting with version 3, Nagios will process plugins' multiline output, which should be formatted as: Output should be in the format: SERVICE STATUS: Information text Verbose output Use the -v flag for verbose output.
Stack Overflow. Framework for evolutionary design.