View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0001495 | CMake | public | 2005-01-18 10:23 | 2005-02-11 21:18 | |||||
Reporter | Eric Wing | ||||||||
Assigned To | Bill Hoffman | ||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0001495: Support (proper handling) for .inl files | ||||||||
Description | While trying to to force Visual Studio to list my header files in my IDE, I started modifying my build process to list all my header files in my ADD_LIBRARY command (workaround for Bug 0001493). Example: ADD_LIBRARY(resourceDB dummy_file.c ResourceDatabase.h ResourceDatabase.inl ) Visual Studio seems to accept this, but when I tested this in gcc however, I got the following error message: CMake Error: Unexpected file type /.../src/memory/ResourceDatabase.inl .inl typically stands for "inline". It is essentially a C++ header file. It's a convention used sometimes to help separate a long inline implementation of class from the declaration. It is also very handy for templates. Admittingly, .inl is not the most widely used extension, but it is a known extension (and not something I made up). I think most distributions of Vi recognize this extension for syntax highlighting by default. It would be great if you could handle this case, as it is rendering my Visual Studio and gcc paths incompatible. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0002056) Bill Hoffman (manager) 2005-02-11 14:22 |
fixed in cvs |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |