Hi Jonah & Doug,
For building the natives on Linux or MacOSX, simply type "make" in the org.eclipse.cdt.core.[macos|linux]/library folder. Test on an "old" machine after rebuilding, to validate you didn't introduce any new dependencies which are missing on older machines.
For Windows, to build winpty and the DLLs see the original contribution in as well as follow-up comments there. I believe Visual Studio 2010 was used at the time. The version of winpty that's currently checked-in is referenced in ipzilla:
Two 1-line fixes were added on top of upstream winpty (as described in the ipzilla) in order to support Windows 10. Integrating a newer version of winpty would make sense from my POV, since IIRC 2 somewhat obscure issues related to foreign charactersets and console resizing were reported over time. Also, the TERM environment variable should not be passed through WindPTY to avoid some confusion.
In the past, contributors always checked-in the binaries that they had built on their own machines. This used to be good enough as there was very rarely a need changing the binaries.
HTH, let me know if you need any more info! Martin
We've avoided having build machines build the native code since for a long time, the foundation didn't have machines that built for all the hosts we supported (e.g. Solaris, AIX, QNX, etc). So whenever someone made a change to the native code, they were responsible for building it themselves or finding friends that had all the machines and checking in the results. That worked because the native code didn't change very often. Now, today, I'm pretty confident in saying we should only support the big three (Windows, Linux, Mac) in x86 and x86_64 with Mac only 64-bit. I assume with the SWT plan, they have machines that build those. For Windows, I've been using the mingw32 cross-compiler on Linux which works well so that makes it even easier. Mind you if I get time to work on the Windows dbgeng.dll integration, I'll need the Windows Build Tools which are Windows only (I believe but these days you never know). All that's needed is someone who has the time to set up the builds. We also need to discuss whether we continue to check in the binaries so others don't need such a complex build environment. Doug. -----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Jonah Graham
Sent: Tuesday, August 29, 2017 3:42 AM
To: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: [cdt-dev] Building native components for CDT
Hi folks,
Does anyone know if/where the process for building the native components for
CDT are?
For example, I am trying to build the winpty support, at the moment the code
for it is not committed[1].
The SWT folk plan in 4.8 (Photon) to move their native builds to Eclipse
Foundation infra[2,3]. I believe it is critical we do the same.
The first step in this is to understand/reproduce the build.
Any insights from those that have built the native components would be greatly
appreciated. I have raised Bug 521515[4] to track this work.
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=419391#c45
[2] https://wiki.eclipse.org/SWT/Plan/4.8
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=520200
[4] https://bugs.eclipse.org/bugs/show_bug.cgi?id=521515
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cdt-dev
|
