Environment variables for java installation

I am able to pass in arguments as follows:

    desc &quot;Testing args&quot;
    task: :hello, :user, :message do |t, args|
      args.with_defaults(:message =&gt; &quot;Thanks for logging on&quot;)
      puts &quot;Hello #{args[:user]}. #{:message}&quot;
    end

I am also able to load the current environment for a Rails application

    desc &quot;Testing environment&quot;
    task: :hello =&gt; :environment do 
      puts &quot;Hello #{User.first.name}.&quot;
    end

What I would like to do is be able to have variables and environment

    desc &quot;Testing environment and variables&quot;
    task: :hello =&gt; :environment, :message do |t, args|
      args.with_defaults(:message =&gt; &quot;Thanks for logging on&quot;)
      puts &quot;Hello #{User.first.name}. #{:message}&quot;
    end

But that is not a valid task call. Does anyone know how I can achieve this?





How to pass arguments into a Rake task with environment in Rails?

I&#39;m working on a project that will read compiler error messages of a particular variety and do useful things with them. The sample codebase I&#39;m testing this on (a random open-source application), and hence rebuilding frequently, contains a few bits that generate warnings, which are of no interest to me.

How do I disable all warnings from GCC, so I can just see error messages if there are any?

Disable all gcc warnings

<p>I'm working on a project that will read compiler error messages of a particular variety and do useful things with them. The sample codebase I'm testing this on (a random open-source application), and hence rebuilding frequently, contains a few bits that generate warnings, which are of no interest to me.</p>
<p>How do I disable all warnings from GCC, so I can just see error messages if there are any?</p>


Why and how is  `__attribute__` used in GNU C programs?

__attribute__ in GNU C

Say I have this small function in a source file

    static void foo() {}

and I build an optimized version of my binary yet I don&#39;t want this function inlined (for optimization purposes). is there a macro I can add in a source code to prevent the inlining?

How can I tell gcc not to inline a function?

I have three files: `program.c`, `program.h` and `headers.h`.

`program.c` includes `program.h` and `headers.h`.

I need to compile this on Linux using _gcc_ compiler.  I&#39;m not sure how to do this. Netbeans created one for me, but it&#39;s empty.

How do I make a simple makefile for gcc on Linux?

I have a cross platform application and in a few of my functions not all the values passed to functions are utilised.  Hence I get a warning from GCC telling me that there are unused variables.

What would be the best way of coding around the warning?

An #ifdef around the function? 

    #ifdef _MSC_VER
    void ProcessOps::sendToExternalApp(QString sAppName, QString sImagePath, qreal qrLeft, qreal qrTop, qreal qrWidth, qreal qrHeight)
    #else
    void ProcessOps::sendToExternalApp(QString sAppName, QString sImagePath, qreal /*qrLeft*/, qreal /*qrTop*/, qreal /*qrWidth*/, qreal /*qrHeight*/)
    #endif
    {

This is so ugly but seems like the way the compiler would prefer.

Or do I assign zero to the variable at the end of the function? (which I hate because it&#39;s altering something in the program flow to silence a compiler warning).

Is there a correct way?

How do I best silence a warning about unused variables?

Due to using Gentoo, it often happens that after an update programs are linked against old versions of libraries. Normally, revdep-rebuild helps resolving that, but this time it&#39;s a dependency on a python library, and `python-updater` won&#39;t pick it up.

Is there a &quot;hierarchical&quot; variant of `ldd` which shows me what shared library depends on which another shared library? Most of the time libraries and executables are linked only against a handful of other shared libraries, which in turn were linked against a handful, turning the library dependency into a big list. I want to know which dependency I&#39;ve got to rebuild with the new version of another library that I upgraded.



Hierarchical ldd(1)

I am getting a lot of these warnings from 3rd party code that I cannot modify.
Is there a way to disable this warning or at least disable it for certain areas (like #pragma push/pop in VC++)?

Example:

    list.h:1122: warning: `list&lt;LogOutput*, allocator&lt;LogOutput*&gt; &gt;::node_alloc_&#39; will be initialized after 
    list.h:1117: warning:   `allocator&lt;LogOutput*&gt; list&lt;LogOutput*, allocator&lt;LogOutput*&gt; &gt;::alloc_&#39;


gcc warning&quot; &#39;will be initialized after&#39;

Ever since I realized many years ago, that this doesn&#39;t produce an error by default (in GCC at least), I&#39;ve always wondered why?

I understand that you can issue compiler flags to produce a warning, but shouldn&#39;t it always be an error? Why does it make sense for a non-void function not returning a value to be valid?

An example as requested in the comments:

    #include &lt;stdio.h&gt;
    int stringSize()
    {
    }
    
    int main()
    {
        char cstring[5];
        printf( &quot;the last char is: %c\n&quot;, cstring[stringSize()-1] ); 
        return 0;
    }

...compiles.



Why does flowing off the end of a non-void function without returning a value not produce a compiler error?

I just found on my Ubuntu, there are two different C++ compilers: `/usr/bin/g++` and `/usr/bin/c++`. I am not familiar with the latter, but `man c++` just jumps to the manpage of gcc. I wonder what is their difference as C++ compilers?


&quot;g++&quot; and &quot;c++&quot; compiler

I am wondering why gcc/g++ doesn&#39;t have an option to place the generated object files into a specified directory.

For example:

    mkdir builddir
    mkdir builddir/objdir
    cd srcdir

    gcc -c file1.c file2.c file3.c **--outdir=**../builddir/objdir

I know that it&#39;s possible to achive this with separate -o options given to the compiler, e.g.:

    gcc -c file1.c -o ../builddir/objdir/file1.o
    gcc -c file2.c -o ../builddir/objdir/file2.o
    gcc -c file3.c -o ../builddir/objdir/file3.o

... and I know that I can write Makefiles via VPATH and vpath directives to simplify this.

But that&#39;s a lot of work in a complex build environment.

I could also use

    gcc -c file1.c file2.c file3.c

But when I use this approach my srcdir is full of .o garbage afterwards.

So I think that an option with the semantics of --outdir would be very useful.

What is your opinion?

**EDIT**: our Makefiles are written in such a way that .o files actually placed into  builddir/obj. But I am simply wondering if there might be a better approach.

**EDIT**: There are several approaches which place the burden to achieve the desired behavior to the build system (aka Make, CMake etc.). But I consider them all as being *workarounds* for a weakness of gcc (and other compilers too).

gcc/g++ option to place all object files into separate directory

The g++ -Wall option includes -Wreorder.  What this option does is described below.  It is not obvious to me why somebody would care (especially enough to turn this on by default in -Wall).

&lt;pre&gt;
-Wreorder (C++ only)
  Warn when the order of member initializers given in the code does not
  match the order in which they must be executed.  For instance:

    struct A {
      int i;
      int j;
      A(): j (0), i (1) { }
    };

  The compiler will rearrange the member initializers for i and j to
  match the declaration order of the members, emit-ting a warning to that
  effect.  This warning is enabled by -Wall.
&lt;/pre&gt;


What&#39;s the point of g++ -Wreorder?

Since upgrading to the latest Xcode 3.2.1 and Snow Leopard, I&#39;ve been getting the warning

&gt; &quot;format not a string literal and no format arguments&quot;

from the following code:


    NSError *error = nil;

    if (![self.managedObjectContext save:&amp;error]) 
    {
    	NSLog([NSString stringWithFormat:@&quot;%@ %@, %@&quot;, 
    	   errorMsgFormat, 
    	   error, 
    	   [error userInfo]]);		

    }

If `errorMsgFormat` is an `NSString` with format specifiers (eg: `&quot;print me like this: %@&quot;`), what is wrong with the above `NSLog` call? And what is the recommended way to fix it so that the warning isn&#39;t generated?



Warning: &quot;format not a string literal and no format arguments&quot;

A warning comes up in a MainMenu.XIB dialogue box.  It says:

`Object: window(window) 
ID: 371
Type: Illegal Configuration
Issue: This windows content rectangle does not lie entirely on the screen with the menu bar and may not be completely visible for all screen resolutions and configurations.`

I saw something related to this issue on StackOverflow, but it did not help.  Here was the prior response:

&gt;In Interface builder select the window and then from the inspector go to the window size tab and move the window away from the left edge. This will get rid of the warning.


Apple Interface Builder warning: The content rectangle doesn&#39;t lie entirely on screen with the menu and may not be completely visible for all screens

With PMD, if you want to ignore a specific warning, you can use `// NOPMD` to have that line be ignored.

Is there something similar for FindBugs?

Is there a way to ignore a single FindBugs warning?

I have a project that uses log4cxx, boost, etc. libraries whose headers generate lots of (repetitive) warnings. Is there a way to suppress warnings from library includes (i.e. #include &amp;lt;some-header.h&amp;gt;) or includes from certain paths? I&#39;d like to use -Wall and/or -Wextra as usual on project code without relevant info being obscured. I currently use grep on make output but I&#39;d like something better.

Content Type	Original Author	Original Content on Stackoverflow
Question	Phil Miller	View Question on Stackoverflow
Solution 1 - Gcc	Phil Miller	View Answer on Stackoverflow

Disable all gcc warnings

Gcc Problem Overview

Gcc Solutions

Solution 1 - Gcc

How to pass arguments into a Rake task with environment in Rails?

Environment variables for java installation

Attributions