Sha256: d286120559aa0840b93da7eac9b9f1956f7f43e1d03e033ce3b52f1435449f8d
Contents?: true
Size: 1.35 KB
Versions: 22
Compression:
Stored size: 1.35 KB
Contents
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <title>Documentation of the bake-tookit</title> </head> <body> <h1>How to create a workspace in Eclipse </h1> <h2>General note</h2> Using bake in Eclipse is very similar compared to the CDT build mechanism. <p> One major difference is, that .cproject and .project files are just wrappers. Do not use the standard property pages, they will be simply ignored! <b>Edit only the Project.meta files.</b><br> <b>The .cproject and .project files shall not be committed to your source control.</b> <h2>Import</h2> If you have a workspace with no .cproject and .project files, but Project.meta files, you can import them to Eclipse. You can also use the importer to import single projects. The importer can be found unter File->Import or in the context menu of the Project Explorer.<br> All (sub)directories with a Project.meta are listed here. Choose the projects to import and press Finish.<p> <img src="import/Select.png"/> <img src="import/Import.png"/><br> <br> Note, that .(c)project files will not be overwritten per default. If e.g. a project is not a c-project, some bake features will not available. In this case, enable the recreate option. This is also a good idea, if you want to get rid of old configurations. </body> </html>
Version data entries
22 entries across 22 versions & 1 rubygems