Bug 271270 - Launch configuration is not being created for project named with dot
Summary: Launch configuration is not being created for project named with dot
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 5.0.2   Edit
Hardware: PC Linux
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
: 279268 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-04-06 00:14 EDT by Alexey CLA
Modified: 2020-09-04 15:21 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey CLA 2009-04-06 00:14:07 EDT
Build ID: I20080617-2000

Steps To Reproduce:
1. Create C++ project
2. Name must contains a dot symbol "."
3. Make some .cpp files (for example "main.cpp") with (for example) following text:
#include <cstdion>

int main(){
  printf("OK!");
  return 0;
}
Run project by Run -> Run from menu. You have the "Launch failed. Binary not found" error.


Ok. Try to "Clean project".
**** Build of configuration Debug for project test.temp ****

make all 
Building file: ../main.cpp
Invoking: GCC C++ Compiler
g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"main.d" -MT"main.d" -o"main.o" "../main.cpp"
Finished building: ../main.cpp
 
Building target: test.temp
Invoking: GCC C++ Linker
g++  -o"test.temp"  ./main.o   
Finished building target: test.temp

Then "Run" project again. And i see "Application Launcher" error again.
And i haven't seen launch configuration for this project "Run -> Run configuration".
Reneming project with no dot created with dot symbol not resolve this problem because build create to old "test.temp" file.
It can resolved only if project create without dot symbol and then renamed with dot. Because build also created old file named without dot (and it create configuration in first Clean project).
Comment 1 Andrew Gvozdev CLA 2009-11-19 21:13:11 EST
*** Bug 279268 has been marked as a duplicate of this bug. ***