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.

Bug 169390 - Can't specify how to compile new file type
Summary: Can't specify how to compile new file type
Status: NEW
Alias: None
Product: cnd
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: issues@cnd
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-28 21:37 UTC by Thomas Preisler
Modified: 2014-04-14 14:31 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Preisler 2009-07-28 21:37:58 UTC
Originally CR 6829629

A DESCRIPTION OF THE REQUEST :
I use corba in my program, so I need to compile IDL files (before any else file type), and then to compile produced cpp files (IDLFileNameC.cpp in client, 
IDLFileNameS.cpp in server). I can do it easy by writing and using makefile directly, but I can't do it from IDE.

JUSTIFICATION :
It will make programming much more convenient.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
There should be option to set command for compiling new file type in Tools->Options->Miscellaneous->Files, in new box bellow Associated File Type 
(MIME). There is such functionality in Codeblocks IDE in Settings->Compiler and Debugger...->Other Settings->Commands in windows Command line 
macro and Generated Files (to be further compiled).  Command line macro and Generated Files should be independent for every configuration.
ACTUAL -
There is no way to specify how to compile new file type from IDE.

CUSTOMER SUBMITTED WORKAROUND :
There is workaround to compile IDLs and produced cpps in pre build stage, and add produced .o files as libraries for linking, but it is not automatic - for 
every added file I must add new .o file for linking, and add new IDL in list of IDLs in pre build stage.


Hi Thomas,

Regards,
Tihomir

You are partially correct about this feature. It really exist, but it must
be set file by file, in file properties. What I asked for was that I can set
it in project or global build options as some kind of macro for all files of
same type. Current state is that I must set it file by file (as it is done
in Yacc/Lex sample) even if all files are of same type (extension). It can
be done, but if there are many such files it becomes cumbersome.
So, in project build options there should be "Custom build steps" tab where
should be possible to define new extension and have all options as in
"Custom build step" tab in file properties. Something like this (ascii art)
:
(Left frame of PROJECT properties: )
        *  General
v      *  Build
           * C compiler
           * C++ compiler
           * Custom build steps   <-------------------- New
           * Fortran compiler
           * Linker
           * Packaging
        *  Run
        *  Debugging
>      *  Advanced

(Right frame of project properties, when Custom build steps is selected in
left frame: )
v      Custom build
v      File extension   [button Remove]| .idl (this is user defined , .idl
just for example)
        Command Line                         | $(HOME)/bin/tao_idl -g
$(HOME)/bin/ -in $file
        Description                               | Compiling idls
        Outputs                                     | $fileC.cpp, $fileC.h
(for client debug and release configurations, for server replace C in names
with S)
        Additional Dependencies          |
>      [button Add new file type]


Thanks for your time!