From: Christiaan H. <cmh...@gm...> - 2018-11-05 08:54:53
|
There weren't any nightly builds for a few days. Is the computer down? Christiaan |
From: Christiaan H. <cmh...@gm...> - 2019-03-08 19:20:02
|
I did not see the last nightly in Dropbox. Were there problems building? There were some changes yesterday for upgrading BibDesk that may give problems, although they should work for Xcode 8. Christiaan |
From: Adam R. M. <ama...@ma...> - 2019-03-11 01:27:32
|
> On Mar 8, 2019, at 11:19 , Christiaan Hofman <cmh...@gm...> wrote: > > I did not see the last nightly in Dropbox. Were there problems building? There were some changes yesterday for upgrading BibDesk that may give problems, although they should work for Xcode 8. Looks like it's complaining about @available, whatever that is? /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:55:9: error: unexpected '@' in program if (@available(macOS 10.8, *)) { ^ /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: warning: 'decodeObjectOfClass:forKey:' is partial: introduced in macOS 10.8 [-Wpartial-availability] NSData *data = [decoder decodeObjectOfClass:[NSData class] forKey:SPUDownloadDataKey]; ^ In module 'Foundation' imported from /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.h:10: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSCoder.h:89:1: note: 'decodeObjectOfClass:forKey:' has been explicitly marked partial here - (nullable id)decodeObjectOfClass:(Class)aClass forKey:(NSString *)key NS_AVAILABLE(10_8, 6_0); ^ /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: note: explicitly redeclare 'decodeObjectOfClass:forKey:' to silence this warning NSData *data = [decoder decodeObjectOfClass:[NSData class] forKey:SPUDownloadDataKey]; |
From: Christiaan H. <cmh...@gm...> - 2019-03-11 08:55:55
|
That's a big problem. I updated Sparkle to the latest, and they say it is compatible with Xcode 8 and runs on 10.7. It looks like that's a lie. These available compiler directives and macros have to do with cross development, a bit like checking for NSAppKitVersionNumber, but on the compiler level. Unfortunately I don't really understand myself how they work. The particular ones have to do with using the newer URL loading API, but only when they're available. Annoyingly I cannot find bug reporting facilities for Sparkle. Op ma 11 mrt. 2019 02:27 schreef Adam R. Maxwell via Bibdesk-develop < bib...@li...: > > > On Mar 8, 2019, at 11:19 , Christiaan Hofman <cmh...@gm...> wrote: > > I did not see the last nightly in Dropbox. Were there problems building? > There were some changes yesterday for upgrading BibDesk that may give > problems, although they should work for Xcode 8. > > > Looks like it's complaining about @available, whatever that is? > > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:55:9: > error: unexpected '@' in program > if (@available(macOS 10.8, *)) { > ^ > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: > warning: 'decodeObjectOfClass:forKey:' is partial: introduced in macOS 10.8 > [-Wpartial-availability] > NSData *data = [decoder decodeObjectOfClass:[NSData class] > forKey:SPUDownloadDataKey]; > ^ > In module 'Foundation' imported from > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.h:10: > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSCoder.h:89:1: > note: 'decodeObjectOfClass:forKey:' has been explicitly marked partial here > - (nullable id)decodeObjectOfClass:(Class)aClass forKey:(NSString *)key > NS_AVAILABLE(10_8, 6_0); > ^ > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: > note: explicitly redeclare 'decodeObjectOfClass:forKey:' to silence this > warning > NSData *data = [decoder decodeObjectOfClass:[NSData class] > forKey:SPUDownloadDataKey]; > > > > > _______________________________________________ > Bibdesk-develop mailing list > Bib...@li... > https://lists.sourceforge.net/lists/listinfo/bibdesk-develop > |
From: Christiaan H. <cmh...@gm...> - 2019-03-11 15:33:42
|
> On 11 Mar 2019, at 09:55, Christiaan Hofman <cmh...@gm...> wrote: > > That's a big problem. I updated Sparkle to the latest, and they say it is compatible with Xcode 8 and runs on 10.7. It looks like that's a lie. These available compiler directives and macros have to do with cross development, a bit like checking for NSAppKitVersionNumber, but on the compiler level. Unfortunately I don't really understand myself how they work. The particular ones have to do with using the newer URL loading API, but only when they're available. Annoyingly I cannot find bug reporting facilities for Sparkle. > > Op ma 11 mrt. 2019 02:27 schreef Adam R. Maxwell via Bibdesk-develop <bib...@li... <mailto:bib...@li...>: > > >> On Mar 8, 2019, at 11:19 , Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote: >> >> I did not see the last nightly in Dropbox. Were there problems building? There were some changes yesterday for upgrading BibDesk that may give problems, although they should work for Xcode 8. > > Looks like it's complaining about @available, whatever that is? > > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:55:9: error: unexpected '@' in program > if (@available(macOS 10.8, *)) { > ^ > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: warning: 'decodeObjectOfClass:forKey:' is partial: introduced in macOS 10.8 [-Wpartial-availability] > NSData *data = [decoder decodeObjectOfClass:[NSData class] forKey:SPUDownloadDataKey]; > ^ > In module 'Foundation' imported from /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.h:10: > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSCoder.h:89:1: note: 'decodeObjectOfClass:forKey:' has been explicitly marked partial here > - (nullable id)decodeObjectOfClass:(Class)aClass forKey:(NSString *)key NS_AVAILABLE(10_8, 6_0); > ^ > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: note: explicitly redeclare 'decodeObjectOfClass:forKey:' to silence this warning > NSData *data = [decoder decodeObjectOfClass:[NSData class] forKey:SPUDownloadDataKey]; > I’ve changed this check to compare the system version rather than using this compiler directive. Hopefully it does now work. Christiaan |
From: Christiaan H. <cmh...@gm...> - 2019-03-12 15:41:44
|
> On 11 Mar 2019, at 16:33, Christiaan Hofman <cmh...@gm...> wrote: > > > >> On 11 Mar 2019, at 09:55, Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote: >> >> That's a big problem. I updated Sparkle to the latest, and they say it is compatible with Xcode 8 and runs on 10.7. It looks like that's a lie. These available compiler directives and macros have to do with cross development, a bit like checking for NSAppKitVersionNumber, but on the compiler level. Unfortunately I don't really understand myself how they work. The particular ones have to do with using the newer URL loading API, but only when they're available. Annoyingly I cannot find bug reporting facilities for Sparkle. >> >> Op ma 11 mrt. 2019 02:27 schreef Adam R. Maxwell via Bibdesk-develop <bib...@li... <mailto:bib...@li...>: >> >> >>> On Mar 8, 2019, at 11:19 , Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote: >>> >>> I did not see the last nightly in Dropbox. Were there problems building? There were some changes yesterday for upgrading BibDesk that may give problems, although they should work for Xcode 8. >> >> Looks like it's complaining about @available, whatever that is? >> >> /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:55:9: error: unexpected '@' in program >> if (@available(macOS 10.8, *)) { >> ^ >> /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: warning: 'decodeObjectOfClass:forKey:' is partial: introduced in macOS 10.8 [-Wpartial-availability] >> NSData *data = [decoder decodeObjectOfClass:[NSData class] forKey:SPUDownloadDataKey]; >> ^ >> In module 'Foundation' imported from /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.h:10: >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSCoder.h:89:1: note: 'decodeObjectOfClass:forKey:' has been explicitly marked partial here >> - (nullable id)decodeObjectOfClass:(Class)aClass forKey:(NSString *)key NS_AVAILABLE(10_8, 6_0); >> ^ >> /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: note: explicitly redeclare 'decodeObjectOfClass:forKey:' to silence this warning >> NSData *data = [decoder decodeObjectOfClass:[NSData class] forKey:SPUDownloadDataKey]; >> > > I’ve changed this check to compare the system version rather than using this compiler directive. Hopefully it does now work. > > Christiaan > Somehow the nightly build still did not appear. Christiaan |
From: Adam R. M. <ama...@ma...> - 2019-03-12 15:45:07
|
> On Mar 12, 2019, at 08:41 , Christiaan Hofman <cmh...@gm...> wrote: > Somehow the nightly build still did not appear. Looks like there are a bunch of these in Sparkle. if (@available(macOS 10.8, *)) { ^ /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUURLRequest.m:76:31: warning: 'decodeObjectOfClass:forKey:' is partial: introduced in macOS 10.8 [-Wpartial-availability] NSURL *url = [decoder decodeObjectOfClass:[NSURL class] forKey:SPUURLRequestURLKey]; $ find . -type f -name "*.m" |xargs grep @available ./Sparkle/Sparkle/SPUURLRequest.m: if (@available(macOS 10.8, *)) { ./Sparkle/Sparkle/SUUpdateAlert.m: if (@available(macOS 10.14, *)) { ./Sparkle/Sparkle/SUUpdateAlert.m: if (@available(macOS 10.14, *)) ./Sparkle/Sparkle/SUUpdateAlert.m: if (@available(macOS 10.14, *)) ./Sparkle/Sparkle/SUUpdater.m: if (@available(macOS 10.9, *)) { |
From: Christiaan H. <cmh...@gm...> - 2019-03-13 09:49:48
|
Cganged them. It nie seems to have worked. Christiaan Op di 12 mrt. 2019 16:45 schreef Adam R. Maxwell via Bibdesk-develop < bib...@li...: > > > On Mar 12, 2019, at 08:41 , Christiaan Hofman <cmh...@gm...> wrote: > Somehow the nightly build still did not appear. > > > Looks like there are a bunch of these in Sparkle. > > if (@available(macOS 10.8, *)) { > ^ > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUURLRequest.m:76:31: > warning: 'decodeObjectOfClass:forKey:' is partial: introduced in macOS 10.8 > [-Wpartial-availability] > NSURL *url = [decoder decodeObjectOfClass:[NSURL class] > forKey:SPUURLRequestURLKey]; > > > $ find . -type f -name "*.m" |xargs grep @available > ./Sparkle/Sparkle/SPUURLRequest.m: if (@available(macOS 10.8, *)) { > ./Sparkle/Sparkle/SUUpdateAlert.m: if (@available(macOS 10.14, *)) { > ./Sparkle/Sparkle/SUUpdateAlert.m: if (@available(macOS 10.14, *)) > ./Sparkle/Sparkle/SUUpdateAlert.m: if (@available(macOS 10.14, *)) > ./Sparkle/Sparkle/SUUpdater.m: if (@available(macOS 10.9, *)) { > _______________________________________________ > Bibdesk-develop mailing list > Bib...@li... > https://lists.sourceforge.net/lists/listinfo/bibdesk-develop > |
From: Christiaan H. <cmh...@gm...> - 2019-03-15 09:47:05
|
It seems to have failed again, niw even with the commit. Christiaan |
From: Adam R. M. <ama...@ma...> - 2019-03-16 03:08:07
|
> On Mar 15, 2019, at 02:46 , Christiaan Hofman <cmh...@gm...> wrote: > > It seems to have failed again, niw even with the commit. svn+ssh error according to the log. That's usually sourceforge. |
From: Adam R. M. <ama...@ma...> - 2018-11-05 15:44:56
|
> On Nov 5, 2018, at 00:54 , Christiaan Hofman <cmh...@gm...> wrote: > > There weren't any nightly builds for a few days. Is the computer down? No, it was working fine yesterday. Any changes to the Xcode project file? It's running an older Xcode on El Capitan, so I'm not sure it's forward compatible with Xcode 10. |
From: Christiaan H. <cmh...@gm...> - 2018-11-05 16:05:32
|
I have clicked away the warnings for xcode 10, but it should still be compatible, I think. Christiaan Op ma 5 nov. 2018 16:45 schreef Adam R. Maxwell via Bibdesk-develop < bib...@li...>: > > > > On Nov 5, 2018, at 00:54 , Christiaan Hofman <cmh...@gm...> wrote: > > > > There weren't any nightly builds for a few days. Is the computer down? > > No, it was working fine yesterday. Any changes to the Xcode project file? > It's running an older Xcode on El Capitan, so I'm not sure it's forward > compatible with Xcode 10. > > > > > > _______________________________________________ > Bibdesk-develop mailing list > Bib...@li... > https://lists.sourceforge.net/lists/listinfo/bibdesk-develop > |
From: Christiaan H. <cmh...@gm...> - 2018-11-05 16:11:13
|
In fact, the project format is still 3.2 compatible. Christiaan > On 5 Nov 2018, at 17:04, Christiaan Hofman <cmh...@gm...> wrote: > > I have clicked away the warnings for xcode 10, but it should still be compatible, I think. > > Christiaan > > Op ma 5 nov. 2018 16:45 schreef Adam R. Maxwell via Bibdesk-develop <bib...@li... <mailto:bib...@li...>>: > > > > On Nov 5, 2018, at 00:54 , Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote: > > > > There weren't any nightly builds for a few days. Is the computer down? > > No, it was working fine yesterday. Any changes to the Xcode project file? It's running an older Xcode on El Capitan, so I'm not sure it's forward compatible with Xcode 10. |
From: Maxwell, A. R <Ada...@pn...> - 2018-11-05 16:34:31
|
I was thinking of the libc++ or whatever change. I’ll try and look at the logs tonight. On Nov 5, 2018, at 08:10, Christiaan Hofman <cmh...@gm...<mailto:cmh...@gm...>> wrote: In fact, the project format is still 3.2 compatible. Christiaan On 5 Nov 2018, at 17:04, Christiaan Hofman <cmh...@gm...<mailto:cmh...@gm...>> wrote: I have clicked away the warnings for xcode 10, but it should still be compatible, I think. Christiaan Op ma 5 nov. 2018 16:45 schreef Adam R. Maxwell via Bibdesk-develop <bib...@li...<mailto:bib...@li...>>: > On Nov 5, 2018, at 00:54 , Christiaan Hofman <cmh...@gm...<mailto:cmh...@gm...>> wrote: > > There weren't any nightly builds for a few days. Is the computer down? No, it was working fine yesterday. Any changes to the Xcode project file? It's running an older Xcode on El Capitan, so I'm not sure it's forward compatible with Xcode 10. _______________________________________________ Bibdesk-develop mailing list Bib...@li...<mailto:Bib...@li...> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop |
From: Christiaan H. <cmh...@gm...> - 2018-11-05 17:11:40
|
Currently libc++ is only used with the 10.14 SDK, older SDKs use libstdc++. Christiaan Op ma 5 nov. 2018 17:34 schreef Maxwell, Adam R <Ada...@pn...>: > I was thinking of the libc++ or whatever change. I’ll try and look at the > logs tonight. > > On Nov 5, 2018, at 08:10, Christiaan Hofman <cmh...@gm...> wrote: > > In fact, the project format is still 3.2 compatible. > > Christiaan > > On 5 Nov 2018, at 17:04, Christiaan Hofman <cmh...@gm...> wrote: > > I have clicked away the warnings for xcode 10, but it should still be > compatible, I think. > > Christiaan > > Op ma 5 nov. 2018 16:45 schreef Adam R. Maxwell via Bibdesk-develop < > bib...@li...>: > >> >> >> > On Nov 5, 2018, at 00:54 , Christiaan Hofman <cmh...@gm...> >> wrote: >> > >> > There weren't any nightly builds for a few days. Is the computer down? >> >> No, it was working fine yesterday. Any changes to the Xcode project file? >> It's running an older Xcode on El Capitan, so I'm not sure it's forward >> compatible with Xcode 10. >> > > > _______________________________________________ > Bibdesk-develop mailing list > Bib...@li... > https://lists.sourceforge.net/lists/listinfo/bibdesk-develop > > > _______________________________________________ > Bibdesk-develop mailing list > Bib...@li... > https://lists.sourceforge.net/lists/listinfo/bibdesk-develop > |
From: Christiaan H. <cmh...@gm...> - 2018-11-05 17:19:55
|
Also, the last nightly build was from 25/10, the last time your computer committed a version bump was 2/11, while I made the changes to the project on 31/10. Three different dates, so they don’t seem to be related. As for the last few days, perhaps there may also be a problem with SF, I get a lot of explicit requests for my password recently, even though it should never have to ask. Christiaan > On 5 Nov 2018, at 18:11, Christiaan Hofman <cmh...@gm...> wrote: > > Currently libc++ is only used with the 10.14 SDK, older SDKs use libstdc++. > > Christiaan > > Op ma 5 nov. 2018 17:34 schreef Maxwell, Adam R <Ada...@pn... <mailto:Ada...@pn...>>: > I was thinking of the libc++ or whatever change. I’ll try and look at the logs tonight. > >> On Nov 5, 2018, at 08:10, Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote: >> >> In fact, the project format is still 3.2 compatible. >> >> Christiaan >> >>> On 5 Nov 2018, at 17:04, Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote: >>> >>> I have clicked away the warnings for xcode 10, but it should still be compatible, I think. >>> >>> Christiaan >>> >>> Op ma 5 nov. 2018 16:45 schreef Adam R. Maxwell via Bibdesk-develop <bib...@li... <mailto:bib...@li...>>: >>> >>> >>> > On Nov 5, 2018, at 00:54 , Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote: >>> > >>> > There weren't any nightly builds for a few days. Is the computer down? >>> >>> No, it was working fine yesterday. Any changes to the Xcode project file? It's running an older Xcode on El Capitan, so I'm not sure it's forward compatible with Xcode 10. >> |
From: Adam R. M. <ama...@ma...> - 2018-11-07 04:26:28
|
> On Nov 5, 2018, at 09:19 , Christiaan Hofman <cmh...@gm...> wrote: > > Also, the last nightly build was from 25/10, the last time your computer committed a version bump was 2/11, while I made the changes to the project on 31/10. Three different dates, so they don’t seem to be related. Whatever the reason, it's choking on C++. I'm not sure if Xcode 10 will work on El Capitan, so this might be the end of that build machine. /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c++ -arch x86_64 -fmessage-length=161 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -fcolor-diagnostics -gmodules -Wno-trigraphs -fpascal-strings -Os -Wno-missing-field-initializers -Wno-missing-prototypes -Wno-implicit-atomic-properties -Wno-arc-repeated-use-of-weak -Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors -Wno-missing-braces -Wparentheses -Wswitch -Wunused-function -Wunused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wno-empty-body -Wuninitialized -Wno-unknown-pragmas -Wshadow -Wno-four-char-constants -Wno-conversion -Wno-constant-conversion -Wno-int-conversion -Wno-bool-conversion -Wno-enum-conversion -Wsign-compare -Wno-shorten-64-to-32 -Wnewline-eof -Wno-selector -Wno-strict-selector-match -Wno-undeclared-selector -Wno-deprecated-implementations -Wno-c++11-extensions -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk -fasm-blocks -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -Winvalid-offsetof -mmacosx-version-min=10.6 -g -fvisibility-inlines-hidden -Wno-sign-conversion -Wno-infinite-recursion -Wno-move -iquote /tmp/obj/FileView.build/Release/FileView.build/FileView-generated-files.hmap -I/tmp/obj/FileView.build/Release/FileView.build/FileView-own-target-headers.hmap -I/tmp/obj/FileView.build/Release/FileView.build/FileView-all-target-headers.hmap -iquote /tmp/obj/FileView.build/Release/FileView.build/FileView-project-headers.hmap -I/tmp/sym/Release/include -I/tmp/obj/FileView.build/Release/FileView.build/DerivedSources/x86_64 -I/tmp/obj/FileView.build/Release/FileView.build/DerivedSources -F/tmp/sym/Release -include /tmp/obj/SharedPrecompiledHeaders/FileView_Prefix-ewbffczggrgiwkccojjhhmbcnytk/FileView_Prefix.pch -MMD -MT dependencies -MF /tmp/obj/FileView.build/Release/FileView.build/Objects-normal/x86_64/FVCacheFile.d --serialize-diagnostics /tmp/obj/FileView.build/Release/FileView.build/Objects-normal/x86_64/FVCacheFile.dia -c /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/amaxwell/FileView/FVCacheFile.mm -o /tmp/obj/FileView.build/Release/FileView.build/Objects-normal/x86_64/FVCacheFile.o /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/amaxwell/FileView/FVCacheFile.mm:127:13: error: use of undeclared identifier 'std' std::string errMsg = std::string("mkstemp failed \"") + tempName + "\""; ^ |
From: Christiaan H. <cmh...@gm...> - 2018-11-07 09:37:38
|
Ah, there is the problem. I think that can be overcome. Either get the std namespace when using older SDKs, or use fprintf to report the errors. Christiaan Op wo 7 nov. 2018 05:26 schreef Adam R. Maxwell via Bibdesk-develop < bib...@li...>: > > > On Nov 5, 2018, at 09:19 , Christiaan Hofman <cmh...@gm...> wrote: > > Also, the last nightly build was from 25/10, the last time your computer > committed a version bump was 2/11, while I made the changes to the project > on 31/10. Three different dates, so they don’t seem to be related. > > > Whatever the reason, it's choking on C++. I'm not sure if Xcode 10 will > work on El Capitan, so this might be the end of that build machine. > > > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang > -x objective-c++ -arch x86_64 -fmessage-length=161 > -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 > -fcolor-diagnostics -gmodules -Wno-trigraphs -fpascal-strings -Os > -Wno-missing-field-initializers -Wno-missing-prototypes > -Wno-implicit-atomic-properties -Wno-arc-repeated-use-of-weak > -Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors > -Wno-missing-braces -Wparentheses -Wswitch -Wunused-function -Wunused-label > -Wno-unused-parameter -Wunused-variable -Wunused-value -Wno-empty-body > -Wuninitialized -Wno-unknown-pragmas -Wshadow -Wno-four-char-constants > -Wno-conversion -Wno-constant-conversion -Wno-int-conversion > -Wno-bool-conversion -Wno-enum-conversion -Wsign-compare > -Wno-shorten-64-to-32 -Wnewline-eof -Wno-selector > -Wno-strict-selector-match -Wno-undeclared-selector > -Wno-deprecated-implementations -Wno-c++11-extensions -isysroot > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk > -fasm-blocks -fstrict-aliasing -Wprotocol -Wdeprecated-declarations > -Winvalid-offsetof -mmacosx-version-min=10.6 -g -fvisibility-inlines-hidden > -Wno-sign-conversion -Wno-infinite-recursion -Wno-move -iquote > /tmp/obj/FileView.build/Release/FileView.build/FileView-generated-files.hmap > -I/tmp/obj/FileView.build/Release/FileView.build/FileView-own-target-headers.hmap > -I/tmp/obj/FileView.build/Release/FileView.build/FileView-all-target-headers.hmap > -iquote > /tmp/obj/FileView.build/Release/FileView.build/FileView-project-headers.hmap > -I/tmp/sym/Release/include > -I/tmp/obj/FileView.build/Release/FileView.build/DerivedSources/x86_64 > -I/tmp/obj/FileView.build/Release/FileView.build/DerivedSources > -F/tmp/sym/Release -include > /tmp/obj/SharedPrecompiledHeaders/FileView_Prefix-ewbffczggrgiwkccojjhhmbcnytk/FileView_Prefix.pch > -MMD -MT dependencies -MF > /tmp/obj/FileView.build/Release/FileView.build/Objects-normal/x86_64/FVCacheFile.d > --serialize-diagnostics > /tmp/obj/FileView.build/Release/FileView.build/Objects-normal/x86_64/FVCacheFile.dia > -c > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/amaxwell/FileView/FVCacheFile.mm > -o > /tmp/obj/FileView.build/Release/FileView.build/Objects-normal/x86_64/FVCacheFile.o > */Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/amaxwell/FileView/FVCacheFile.mm:127:13: > **error: **use of undeclared identifier 'std'* > std::string errMsg = std::string("mkstemp failed \"") + > tempName + "\""; > * ^* > > > _______________________________________________ > Bibdesk-develop mailing list > Bib...@li... > https://lists.sourceforge.net/lists/listinfo/bibdesk-develop > |
From: Christiaan H. <cmh...@gm...> - 2018-11-07 12:45:14
|
This should be fixed now, I forgot to put the <string> import back. A bit surprising that with libc++ it works without this. Christiaan |
From: Christiaan H. <cmh...@gm...> - 2018-11-08 10:47:32
|
Why didn't it work now? Any relevant changes shouldn't be active when using an older SDK. Christiaan Op wo 7 nov. 2018 13:44 schreef Christiaan Hofman <cmh...@gm...>: > This should be fixed now, I forgot to put the <string> import back. A bit > surprising that with libc++ it works without this. > > Christiaan > > |
From: Adam R. M. <ama...@ma...> - 2018-11-08 14:14:24
|
> On Nov 8, 2018, at 02:46 , Christiaan Hofman <cmh...@gm...> wrote: > > Why didn't it work now? Any relevant changes shouldn't be active when using an older SDK. It looks like NSPasteboardType doesn't exist in the SDK. /Volumes/Local/Users/amaxwell/build/bibdesk-clean/BDSKPersonController.m:503:93: error: expected a type - (void)pasteboard:(NSPasteboard *)pboard item:(NSPasteboardItem *)item provideDataForType:(NSPasteboardType)type { ^ |
From: Christiaan H. <cmh...@gm...> - 2018-11-08 14:56:58
|
> On 8 Nov 2018, at 15:14, Adam R. Maxwell <ama...@ma...> wrote: > > > >> On Nov 8, 2018, at 02:46 , Christiaan Hofman <cmh...@gm...> wrote: >> >> Why didn't it work now? Any relevant changes shouldn't be active when using an older SDK. > > It looks like NSPasteboardType doesn't exist in the SDK. > > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/BDSKPersonController.m:503:93: error: expected a type > - (void)pasteboard:(NSPasteboard *)pboard item:(NSPasteboardItem *)item provideDataForType:(NSPasteboardType)type { > I get really annoyed by Apple defining a separate type for everything. And then their docs don’t even say WHEN they defined that type, they just lie about it. And then the compiler complains when you don’t use that type because your older system does not support it. Of course the header says that the NSPasteboardType was defined on 10.6+, that’s just a lie. Christiaan |
From: Maxwell, A. R <Ada...@pn...> - 2018-11-08 16:12:51
|
On Nov 8, 2018, at 06:56, Christiaan Hofman <cmh...@gm...> wrote: > > On 8 Nov 2018, at 15:14, Adam R. Maxwell <ama...@ma...> wrote: >> >> >> It looks like NSPasteboardType doesn't exist in the SDK. >> >> /Volumes/Local/Users/amaxwell/build/bibdesk-clean/BDSKPersonController.m:503:93: error: expected a type >> - (void)pasteboard:(NSPasteboard *)pboard item:(NSPasteboardItem *)item provideDataForType:(NSPasteboardType)type { >> > > I get really annoyed by Apple defining a separate type for everything. And then their docs don’t even say WHEN they defined that type, they just lie about it. And then the compiler complains when you don’t use that type because your older system does not support it. Of course the header says that the NSPasteboardType was defined on 10.6+, that’s just a lie. Yeah, I wouldn’t have realized that didn’t exist on older SDKs, based on the header. There’s so much Swift crap in there that they’re as unreadable as C++. I remember hating -valueForKeyPath: because you’d lose help from the compiler, but I think they’ve gone way overboard here with type insanity. -- adam |
From: Christiaan H. <cmh...@gm...> - 2018-11-09 21:32:46
|
> On 8 Nov 2018, at 17:04, Maxwell, Adam R <ada...@pn...> wrote: > > On Nov 8, 2018, at 06:56, Christiaan Hofman <cmh...@gm...> wrote: >> >> On 8 Nov 2018, at 15:14, Adam R. Maxwell <ama...@ma...> wrote: >>> >>> >>> It looks like NSPasteboardType doesn't exist in the SDK. >>> >>> /Volumes/Local/Users/amaxwell/build/bibdesk-clean/BDSKPersonController.m:503:93: error: expected a type >>> - (void)pasteboard:(NSPasteboard *)pboard item:(NSPasteboardItem *)item provideDataForType:(NSPasteboardType)type { >>> >> >> I get really annoyed by Apple defining a separate type for everything. And then their docs don’t even say WHEN they defined that type, they just lie about it. And then the compiler complains when you don’t use that type because your older system does not support it. Of course the header says that the NSPasteboardType was defined on 10.6+, that’s just a lie. > > Yeah, I wouldn’t have realized that didn’t exist on older SDKs, based on the header. There’s so much Swift crap in there that they’re as unreadable as C++. I remember hating -valueForKeyPath: because you’d lose help from the compiler, but I think they’ve gone way overboard here with type insanity. > > — adam > I replaced NSPasteboardType. But it still does not seem to work? Christiaan |
From: Maxwell, A. R <Ada...@pn...> - 2018-11-09 22:32:36
|
On Nov 9, 2018, at 13:32, Christiaan Hofman <cmh...@gm...<mailto:cmh...@gm...>> wrote: I replaced NSPasteboardType. But it still does not seem to work? I'll try and build it tonight or tomorrow and see if I can fix it. Sorry for just checking the logs and firing off errors…I just haven't had any time at home this week. |