jmramosr/pro-c-for-eclipse

Pro*C plugin for Eclipse.

Pro-C-for-Eclipse: Pro*C plugin for Eclipse.

This repository contains a complete Eclipse workspace to compile successfully the Pro*C plugin. I don't code in Java, but you can send pull requests to make this plugin better.

Original work by https://github.com/buntatsu/cdt-proc. The firsts commits are, indeed, the original repo.

How to compile the plugin

🔘 You will need a computer with JDK installed. I suggest a list I tested it and it works. You can simply ignore it and use the most recent JDK. I tested on Windows, but you can use a osX or the Linux flavor you want.

🔘 Download from https://www.eclipse.org/downloads/packages/release the package you want. Ensure you choose the Eclipse IDE for Eclipse Committers version.

🔘 Open your Eclipse IDE for Eclipse Committers, create an empty workspace and install the version of CDT you want to use. You must install, at least, the main features. Restart the program.

🔘 Go here and select the branch which name contains the name of your CDT version.

🔘 Download the branch. It contains a workspace inside the branch.

🔘 Open your Eclipse IDE for Eclipse Committers and open the workspace. Wait until completes the building of the workspace. It probably doesn't have the auto build.

🔘 Select in any project the export option -> Deployable plugins and fragments -> select all -> Directory -> Select the directory -> Click Finish.

🔘 Wait until completion and now you have your plugin ready in the folder you provided!

How to use the compiled plugin

🔘 Download from https://www.eclipse.org/downloads/packages/release the package you want and install it. You will need the Eclipse IDE for C/C++ Developers version

🔘 When you finish the installation, go to the plugins folder and find a file starts like this: org.eclipse.cdt.core_X.Y.Z.YYYYMMDDhhmm.jar. X.Y.Z stands for the version. Annotate the date.

🔘 Go here and download the release with that version, if I have it.

🔘 If I don't have it, submit an issue. Submit the name of your org.eclipse.cdt_X.Y.Z.YYYYMMDDhhmm.jar file, not the org.eclipse.cdt.core_X.Y.Z.YYYYMMDDhhmm.jar one!

🔘 Replace the org.eclipse.cdt.core_X.Y.Z.YYYYMMDDhhmm.jar and copy the other ones. Backup first the org.eclipse.cdt.core_X.Y.Z.YYYYMMDDhhmm.jar file if you don't feel confident.

How to upgrade the plugin with Eclipse CDT

🔘 Update CDT to the release version you want. This step assumes you have the version Eclipse IDE for C/C++ Developers for your package. If you have been installed a previous Pro*C plugin for Eclipse in this version, restore the original org.eclipse.cdt.core_X.Y.Z.YYYYMMDDhhmm.jar.

🔘 Search in your plugins folder the lastest org.eclipse.cdt.core_X.Y.Z.YYYYMMDDhhmm.jar. You will have, at least, 2 versions of the file org.eclipse.cdt.core_X.Y.Z.YYYYMMDDhhmm.jar.

🔘 Search in the releases list the lastest CDT version you have and download it.

🔘 Replace the org.eclipse.cdt.core_X.Y.Z.YYYYMMDDhhmm.jar and copy the other ones. Backup first the org.eclipse.cdt.core_X.Y.Z.YYYYMMDDhhmm.jar file if you don't feel confident.

Version List

Package	Compilated package numbers
CDT_9_6_0	org.eclipse.cdt_9.6.0.201811241055.jar
CDT_9_5_5	org.eclipse.cdt_9.5.5.201811180605.jar
CDT_9_5_4	org.eclipse.cdt_9.5.4.201810050005.jar
CDT_9_5_3	org.eclipse.cdt_9.5.3.201809121146.jar
CDT_9_5_2	org.eclipse.cdt_9.5.2.201807181141.jar
CDT_9_5_1	org.eclipse.cdt_9.5.1.201807051742.jar
CDT_9_5_0	org.eclipse.cdt_9.5.0.201806170908.jar
CDT_9_4_3	org.eclipse.cdt_9.4.3.201802261533.jar
CDT_9_4_2	org.eclipse.cdt_9.4.2.201802122019.jar
CDT_9_4_1	org.eclipse.cdt_9.3.0.201801130900.jar
CDT_9_4_0	org.eclipse.cdt_9.3.0.201712020452.jar

Warnings

⬜️ Be careful about CDT_9_4_1 and CDT_9_4_0! They use the same names with different dates. That's why you can annotate the release date, it serves as reference number for me.

TODO

✔️ Get the version numbers of each package and make the version list.

✔️ Renaming the original plugin.

✔️ Upload every version.

❌️ Buglist of everyday use.

❌️ Not modifying the original org.eclipse.cdt.core_X.Y.Z.YYYYMMDDhhmm.jar to use this plugin.

JDK Used:

All CDT versions uses JDK 1.8 to compile them, as you can see in the manifest.mf files in each version.

pro-c-for-eclipse's Issues

Upgrade to CDT 8.3 ???

Hi Jose Ramos,

Do you have any plans to upgrade your plugin to work with the latest CDT version ?

Missing updates in CPreprocessor?

H, I've been trying to get the cdt 9.5.2 (for Eclispse Photon) version of the ProC plugin to work from the source code (I have no access to the compiled version in the development environment). Using the source as-is does not give any syntax highlighting and all proC statements are labelled as syntax errors. After some hour debugging I finally resorted to adding newLexer() methods to the org.eclipse.cdt.internal.core.parser.scanner.CPreprocessor class and using them to instantiate the Lexer in the CPreprocessor constructor - miracle or miracles I now have syntax highlighting and no more syntax errors in my proC source!
I've checked back with an old version of the buntatsu and indeed it does have newLexer methods in org.eclipse.cdt.internal.core.parser.scanner.CPreprocessor which are not present in the original eclipse code.

Was something missed when the updated eclipse source was transferred here? Am I missing something in how the ProC plugin is intended to work? I only have access to eclipse Photon at the moment so do not know whether the same problem exists in more recent versions.

Any chance that the changes to the eclipse CDT code could be submitted to eclipse so there is no longer a need to have a different version? From what I can see the changes are trivial, mostly to do with allowing sub-class access to the (pre)processor classes, plus the addition of the newLexer methods to allow the Lexer to be overriden?

Regards,,
Chris
BTW thanks for making the project available!!!