This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Especially for cross compiling the specification of the ranlib executable should be possible per compiler toolset. See also Bug # 180922 (prohibits giving the compiler specific ar the flag to perform ranlib).
Fixed first part: name of ranlib tool is now configurable from the project properties. Now you can go the the project properties under Archiver and change the Indexer tool from 'ranlib' to whatever for a particular configuration. This provides you with a way to add your own indexer for a particular compiler set. Note: for this to work, you need to remove the line "RANLIB=ranlib" from master makefile in t=your project root if you are using an already generated project. Next step is to define ranlib in the toolchain and have the toolchain automatically fill this field out. See also 169151.
Change component to toolchain and also dropping to p4.
Integrated into 'main-golden', will be available in build *201004220200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/c231bb393e7d User: Thomas Preisler <thp@netbeans.org> Log: #180926 - ranlib executable definition should be compiler specific
Is this request still open, because I would need it for Visual C++ compiler (VCC4N) so I can archive static libraries using another compiler. Of course I can, replace ar and uncheck "run ranlib", but it would be easier if this was automatically created with the toolchain, so people don't have to do it manually and for every project, which is annoying. This idea is to add it to the toolchain, so you can specify an archiver, indexer (optional) and arguments (including the platform). Should we keep this one or create a new request?