Re: include files for cgxCADTools

k directories etc > > Rob > From: macports-dev on behalf of > Mark Brethen > Sent: August 8, 2022 12:22 PM > To: Joshua Root > Cc: MacPorts Developers > Subject: Re: include files for cgxCADTools > > The makefile only sets cc, not c++. If I remove -lstc++ from

Re: include files for cgxCADTools

If you're patching the Makefile, patch it to use $CXX when building C++ code. - Josh On 2022-8-9 02:22 , Mark Brethen wrote: The makefile only sets cc, not c++. If I remove -lstc++ from LIBS, then I need to add it to the portfile using LDFLAGS. The Makefile uses LFLAGS, which I don’t want to

Re: include files for cgxCADTools

Okay, this setup worked: Portfile Description: Binary data patch-FbdReader-build.diff Description: Binary data main.log Description: Binary data Mark Brethenmark.bret...@gmail.com On Aug 8, 2022, at 12:25 PM, Mark Brethen wrote:Robert,I assume FWORKDIRS needs to be

Re: include files for cgxCADTools

. -lm for math library FWORKDIRS += Framework directories etc Rob From: macports-dev on behalf of Mark Brethen Sent: August 8, 2022 12:22 PM To: Joshua Root Cc: MacPorts Developers Subject: Re: include files for cgxCADTools The makefile only sets cc, not c++. If

Re: include files for cgxCADTools

Well, that didn’t work. main.log Description: Binary data Portfile Description: Binary data patch-FbdReader-build.diff Description: Binary data Mark Brethen mark.bret...@gmail.com > On Aug 8, 2022, at 11:22 AM, Mark Brethen wrote: > > The makefile only sets cc, not c++. If I remove -ls

Re: include files for cgxCADTools

The makefile only sets cc, not c++. If I remove -lstc++ from LIBS, then I need to add it to the portfile using LDFLAGS. The Makefile uses LFLAGS, which I don’t want to override. Should I add LDFLAGS to MAIN, like so: $(MAIN): $(OBJS) $(CC) $(CFLAGS) $(INCLUDES) -o $(MAIN) $(OBJS) $(LFLA

Re: include files for cgxCADTools

That's a completely different thing. The language standard is selected by -std, the stdlib implementation is selected by -stdlib, and linking to a stdlib directly (as -lstdc++ does) is usually a bug since the C++ compiler will implicitly add the appropriate stdlib when linking. - Josh On 2022

Re: include files for cgxCADTools

There is also -lstdc++, I thought those should be set in the Portfile. Doesn’t macports-clang have its own standard? Mark Brethen mark.bret...@gmail.com > On Aug 7, 2022, at 7:22 PM, Ryan Schmidt wrote: > > In fact, the Makefile already had -std=c++11, but your patchfile removed it. > So d

Re: include files for cgxCADTools

Build results with minimal patch of Makefile. Note in Portfile I have a single build.args-append statement. main.log Description: Binary data Portfile Description: Binary data patch-FbdReader-build.diff Description: Binary data Mark Brethen mark.bret...@gmail.com > On Aug 7, 2022, at 7

Re: include files for cgxCADTools

Interestingly, the Makefile only defined CC, even though the source is c++. Is that typical done? Mark Brethen mark.bret...@gmail.com > On Aug 7, 2022, at 7:18 PM, Ryan Schmidt wrote: > > Why not let make's default value for CXX be used if the user (or in this case > MacPorts) doesn't spe

Re: include files for cgxCADTools

On Aug 7, 2022, at 19:06, Ryan Schmidt wrote: > configure.cxxflags-append -std=c++11 In fact, the Makefile already had -std=c++11, but your patchfile removed it. So don't remove it.

Re: include files for cgxCADTools

On Aug 6, 2022, at 09:47, Mark Brethen wrote: > See log file for errors I’m getting with using build.env instead of > build.args. The log has errors like this: Os -arch x86_64 -Wall -I../../FbdReader/inc -I/opt/local/include/opencascade -c FbdReader.cpp -o FbdReader.o make: Os: No such file

Re: include files for cgxCADTools

On Aug 6, 2022, at 12:14, Mark Brethen wrote: > > It builds successfully when I blacklist Apple’s clang. It used clang++ 14, which I think defaults to a newer language standard. So don't blacklist Apple clang. Instead, specify what language standard you want, per my previous message.

Re: include files for cgxCADTools

On Aug 6, 2022, at 12:09, Mark Brethen wrote: > Here’s the log file when using build.args instead of build.env and compiling > with Apple’s clang. Different failure this time. You're getting warning about C++11 features: /opt/local/include/opencascade/Standard_Handle.hxx:75:19: warning: rva

Re: include files for cgxCADTools

If passing build.env, need to remove cc, cxx, etc. assignments in makefile. Even ‘cc=‘ will cause those errors. Mark Brethen mark.bret...@gmail.com > On Aug 6, 2022, at 9:47 AM, Mark Brethen wrote: > > See log file for errors I’m getting with using build.env instead of > build.args. > >

Re: include files for cgxCADTools

It builds successfully when I blacklist Apple’s clang. Portfile Description: Binary data main.log Description: Binary data Mark Brethen mark.bret...@gmail.com > On Aug 6, 2022, at 12:09 PM, Mark Brethen wrote: > > Here’s the log file when using build.args instead of build.env and compil

Re: include files for cgxCADTools

Here’s the log file when using build.args instead of build.env and compiling with Apple’s clang. Different failure this time. main.log Description: Binary data Portfile Description: Binary data patch-FbdReader-build.diff Description: Binary data Mark Brethen mark.bret...@gmail.com > On

Re: include files for cgxCADTools

See log file for errors I’m getting with using build.env instead of build.args. Portfile Description: Binary data patch-FbdReader-build.diff Description: Binary data main.log Description: Binary data Mark Brethen mark.bret...@gmail.com > On Aug 5, 2022, at 3:30 PM, Ryan Schmidt wrote: >

Re: include files for cgxCADTools

On Aug 5, 2022, at 15:26, Mark Brethen wrote: > > I don’t see these errors when building with macports-clang, only Apple’s > clang. Ok. Certainly, different compilers can behave differently. I didn't try to see what the actual error was, since it was jumbled. If you have an non-jumbled error m

Re: include files for cgxCADTools

I don’t see these errors when building with macports-clang, only Apple’s clang. Mark Brethen mark.bret...@gmail.com > On Aug 5, 2022, at 3:09 PM, Ryan Schmidt wrote: > > On Aug 4, 2022, at 13:19, Mark Brethen wrote: > >> I’m seeing this error when generate all the header dependencies for >>

Re: include files for cgxCADTools

On Aug 4, 2022, at 13:19, Mark Brethen wrote: > I’m seeing this error when generate all the header dependencies for > FbdReader. This is confusing, which file has the error? Error messages from several different files are being jumbled together due to parallel building. You can make it less con

Re: include files for cgxCADTools

On 2022-8-5 09:05 , Mark Brethen wrote: I have a stub that installs the documentation files and both subports but I get these warning messages. How should I fix? The following dependencies will be installed:  CadReader  FbdReader Continue? [Y/n]: --->  Fetching distfiles for CadReader --->  V

Re: include files for cgxCADTools

rt Kennedy <am...@hotmail.com> wrote:Mark,I was able to spend more time with your Makefile.  I corrected some typos.Attached is the FINAL Makefile Rev 4 along with the patch file (that will patch the original Makefile)It should work well for your purposes.If you are having trouble with the ex

Re: include files for cgxCADTools

<mailto:mark.bret...@gmail.com> >>> >>> >>> >>>> On Aug 2, 2022, at 6:20 PM, Robert Kennedy >>> <mailto:am...@hotmail.com>> wrote: >>>> >>>> Mark, >>>> >>>> I was able to spend more time wi

Re: include files for cgxCADTools

I corrected some typos. >>> >>> Attached is the FINAL Makefile Rev 4 along with the patch file (that will >>> patch the original Makefile) >>> >>> It should work well for your purposes. >>> >>> If you are having trouble with the extr

Re: include files for cgxCADTools

f your Portfile and I will take a look. It can be frustrating when things >> do not unpack as expected.\\ >> >> Rob >> >> From: Mark Brethen mailto:mark.bret...@gmail.com>> >> Sent: August 2, 2022 4:51 PM >> To: Robert Kennedy mailto:am...@hotmail.com&g

Re: include files for cgxCADTools

gust 2, 2022 3:46 PMTo: Mark Brethen <mark.bret...@gmail.com>Subject: Re: include files for cgxCADTools Mark,Since it is a C++ project (not a C project), I modified the Makefile accordingly. See attached.Please note that I added LDFLAGS = -stdlib=libc++ and added $LDFLAGS to the Makefile target that d

Re: include files for cgxCADTools

2 3:46 PM > To: Mark Brethen > Subject: Re: include files for cgxCADTools > > Mark, > > Since it is a C++ project (not a C project), I modified the Makefile > accordingly. See attached. > > Please note that I added LDFLAGS = -stdlib=libc++ and added $LDFLAGS to the &

Re: include files for cgxCADTools

00 PM To: Robert Kennedy Cc: MacPorts Developers Subject: Re: include files for cgxCADTools I stripped those lines but there were some glitches in the build. First the Makefile only defines CC but the source is c++. :info:build /opt/local/include/opencascade/Standard_Handle.hxx:75:19: wa

Re: include files for cgxCADTools

project from >> scratch. (i.e. build all the objects and then link them into the final >> product). >> >> In my view, Macports was not designed for development but for building a >> finished project and making a binary package. (i.e. package management) >>

Re: include files for cgxCADTools

Macports to build that:   macports: depends all  And in the portfile, you would add: build.targetmacports Good luck, Rob ________________ From: macports-dev on behalf of Mark Brethen Sent: August 1, 2022 8:51 PM To: MacPorts Developers Subject: Re: include files for cgxCADTools I’

Re: include files for cgxCADTools

e portfile, you would add: build.targetmacports Good luck, Rob ____ From: macports-dev on behalf of Mark Brethen Sent: August 1, 2022 8:51 PM To: MacPorts Developers Subject: Re: include files for cgxCADTools I’ll ask the developer Sent from my iPhone >

Re: include files for cgxCADTools

I’ll ask the developer Sent from my iPhone > On Aug 1, 2022, at 4:53 PM, Joshua Root wrote: > > A lot of them aren't even standard headers; I believe the ones under bits/ > are glibc implementation details. I would suspect this part of the Makefile > was not hand-written but generated with o

Re: include files for cgxCADTools

A lot of them aren't even standard headers; I believe the ones under bits/ are glibc implementation details. I would suspect this part of the Makefile was not hand-written but generated with one of the compiler's -M options. To work correctly in that case, it would need to be regenerated for ea

Re: include files for cgxCADTools

The top of the makefile looks normal enough, then it lists a boat-load of headers. I guess I won’t spend any more time on it. Mark Brethen mark.bret...@gmail.com > On Aug 1, 2022, at 2:23 PM, Chris Jones wrote: > > > The makefile here is very poorly written. You should never directly refe

Re: include files for cgxCADTools

The makefile here is very poorly written. You should never directly reference standard headers like that… > On 1 Aug 2022, at 4:52 pm, Mark Brethen wrote: > > This Makefile has the following lines: > > CadReader.o: /usr/include/stdlib.h /usr/include/bits/libc-header-start.h > CadReader.o: /u