You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(13) |
Nov
(42) |
Dec
(18) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(12) |
Feb
(2) |
Mar
(9) |
Apr
(3) |
May
(3) |
Jun
(5) |
Jul
(13) |
Aug
(10) |
Sep
(5) |
Oct
(39) |
Nov
(44) |
Dec
(59) |
2004 |
Jan
(15) |
Feb
(44) |
Mar
(163) |
Apr
(74) |
May
(19) |
Jun
(53) |
Jul
(110) |
Aug
(173) |
Sep
(157) |
Oct
(74) |
Nov
(243) |
Dec
(326) |
2005 |
Jan
(112) |
Feb
(274) |
Mar
(336) |
Apr
(547) |
May
(465) |
Jun
(226) |
Jul
(227) |
Aug
(348) |
Sep
(134) |
Oct
(229) |
Nov
(202) |
Dec
(127) |
2006 |
Jan
(56) |
Feb
(136) |
Mar
(113) |
Apr
(133) |
May
(149) |
Jun
(59) |
Jul
(31) |
Aug
(134) |
Sep
(47) |
Oct
(132) |
Nov
(92) |
Dec
(72) |
2007 |
Jan
(193) |
Feb
(258) |
Mar
(213) |
Apr
(103) |
May
(84) |
Jun
(27) |
Jul
(40) |
Aug
(59) |
Sep
(62) |
Oct
(64) |
Nov
(105) |
Dec
(148) |
2008 |
Jan
(262) |
Feb
(35) |
Mar
(44) |
Apr
(27) |
May
|
Jun
(37) |
Jul
(10) |
Aug
(29) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
2009 |
Jan
(149) |
Feb
(53) |
Mar
(92) |
Apr
(69) |
May
(34) |
Jun
(51) |
Jul
(48) |
Aug
(44) |
Sep
(35) |
Oct
(25) |
Nov
(31) |
Dec
(14) |
2010 |
Jan
(13) |
Feb
(29) |
Mar
(2) |
Apr
(3) |
May
(9) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
(4) |
Dec
|
2011 |
Jan
|
Feb
|
Mar
(7) |
Apr
(6) |
May
(2) |
Jun
(2) |
Jul
(7) |
Aug
(10) |
Sep
(5) |
Oct
(3) |
Nov
(2) |
Dec
(5) |
2012 |
Jan
(17) |
Feb
(3) |
Mar
(11) |
Apr
(6) |
May
(23) |
Jun
(13) |
Jul
(10) |
Aug
(13) |
Sep
(5) |
Oct
(14) |
Nov
(27) |
Dec
(12) |
2013 |
Jan
(44) |
Feb
(41) |
Mar
|
Apr
(8) |
May
(5) |
Jun
(31) |
Jul
|
Aug
(11) |
Sep
(1) |
Oct
|
Nov
(16) |
Dec
(34) |
2014 |
Jan
|
Feb
|
Mar
(90) |
Apr
(57) |
May
(10) |
Jun
(5) |
Jul
(12) |
Aug
(5) |
Sep
(8) |
Oct
|
Nov
|
Dec
(1) |
2015 |
Jan
|
Feb
(8) |
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
(10) |
Aug
(2) |
Sep
|
Oct
(30) |
Nov
|
Dec
|
2016 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
(21) |
May
|
Jun
(3) |
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
(5) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(10) |
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(9) |
Nov
(20) |
Dec
|
2019 |
Jan
|
Feb
(4) |
Mar
(9) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
2021 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
2022 |
Jan
(3) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
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. |
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-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-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: 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 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: 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-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: 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-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: 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: 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 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: 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: 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 08:54:53
|
There weren't any nightly builds for a few days. Is the computer down? Christiaan |
From: Christiaan H. <cmh...@gm...> - 2018-10-31 20:00:56
|
> On 31 Oct 2018, at 19:41, Maxwell, Adam R <ada...@pn...> wrote: > > > >> On Oct 31, 2018, at 11:21, Christiaan Hofman <cmh...@gm...> wrote: >> >> I did change the new/delete with malloc/free, so that gets rid of the errors at least. doesn’t libc++ know about new/delete? > > You have to change the file extension from .m to .mm, so it knows it’s Obj-C++. That gets rid of the new/delete error. > Stupid, I forgot that was the file I changed, and overlooked the new/delete. >> But now I get a host of warnings about deprecated methods for 10.7. > > Yeah, those are from Apple’s push to rename methods that have been around FOREVER. Possibly because the documentation is no good anymore. I mean > -[NSWindow convertBaseToScreen:] has been there since 10.0, and the documentation now says to use -[NSWindow convertRectToScreen:] instead. The header says you can also use -[NSWindow convertPointToScreen:], but that has no documentation except that it’s 10.12+ only. WTF is this. > > — adam Ah, I actually did not notice the 10.12+, that is truly stupid. Fortunately they did define convertRectToScreen: on 10.7+. And as far as the documentation, I get the impression the complete documentation misses all descriptions for some time now. And that’s even true for the Swift versions. Christiaan |
From: Maxwell, A. R <Ada...@pn...> - 2018-10-31 18:41:16
|
> On Oct 31, 2018, at 11:21, Christiaan Hofman <cmh...@gm...> wrote: > > I did change the new/delete with malloc/free, so that gets rid of the errors at least. doesn’t libc++ know about new/delete? You have to change the file extension from .m to .mm, so it knows it’s Obj-C++. That gets rid of the new/delete error. > But now I get a host of warnings about deprecated methods for 10.7. Yeah, those are from Apple’s push to rename methods that have been around FOREVER. Possibly because the documentation is no good anymore. I mean -[NSWindow convertBaseToScreen:] has been there since 10.0, and the documentation now says to use -[NSWindow convertRectToScreen:] instead. The header says you can also use -[NSWindow convertPointToScreen:], but that has no documentation except that it’s 10.12+ only. WTF is this. — adam |
From: Christiaan H. <cmh...@gm...> - 2018-10-31 18:21:42
|
> On 31 Oct 2018, at 19:17, Maxwell, Adam R <Ada...@pn...> wrote: > > >> On Oct 31, 2018, at 10:54, Christiaan Hofman <cmh...@gm...> wrote: >> >> Unfortunately I also cannot make it work with libc++ and 10.6 dropped. I get a stupid warning about incompatible pointer types in FVCacheFile (even though there’s a clang diagnostic ignored), and more problematic, the new and delete don’t work in FVCacheFile. Any ideas? > > Huh. The FVCacheFile.m in BibDesk’s repo looks like ObjC only? If you add the C++ stuff from my github project, make sure to change the filename or tell Xcode it’s ObjC++. That’s the only thing I can think of. I don’t think that warning has anything to do with C++, only with 10.7+. But I really have no idea about this warning, especially with the pragmas. I did change the new/delete with malloc/free, so that gets rid of the errors at least. doesn’t libc++ know about new/delete? But now I get a host of warnings about deprecated methods for 10.7. Christiaan |
From: Maxwell, A. R <Ada...@pn...> - 2018-10-31 18:17:37
|
> On Oct 31, 2018, at 10:54, Christiaan Hofman <cmh...@gm...> wrote: > > Unfortunately I also cannot make it work with libc++ and 10.6 dropped. I get a stupid warning about incompatible pointer types in FVCacheFile (even though there’s a clang diagnostic ignored), and more problematic, the new and delete don’t work in FVCacheFile. Any ideas? Huh. The FVCacheFile.m in BibDesk’s repo looks like ObjC only? If you add the C++ stuff from my github project, make sure to change the filename or tell Xcode it’s ObjC++. That’s the only thing I can think of. |
From: Christiaan H. <cmh...@gm...> - 2018-10-31 17:54:44
|
> On 31 Oct 2018, at 18:30, Maxwell, Adam R <ada...@pn...> wrote: > > > >> On Oct 31, 2018, at 10:05, Christiaan Hofman <cmh...@gm...> wrote: >> >> >> I know exactly nothing about NSZone. I wonder how much the efficiency gains in fvzone are needed with newer OS versions. > > Last time I profiled it, it was still a decent performance win (Sierra, I think). NSZone is really optimized around tiny mallocs, for NSObject sizes rather than bitmap image sizes. Running FVAllocatorPerf on a 3.5 GHz Mac Pro with 10.13, I get: > > FVAllocator: 3.52 seconds for 20000 iterations > CFAllocator: 6.21 seconds for 20000 iterations > >> I am glad I made a copy of Xcode 9 before updating to 10. But I probably will drop 10.6 anyway. That also solves my problem with ppc support that’s still there, and Sparkle does not check for architecture support (though I wonder if there’s even a single user for that, my last PPC machine died long ago). So dropping 10.6 will also ignore new releases for anyone using ppc, as that requires 10.6. > > BibDesk still had PPC support? I thought Xcode had dropped that years ago! FWIW, the MacTeX working group recently decided that MacTeX would officially support only versions of OS X for which Apple still provides security patches. Compiling, packaging, and testing had basically become impossible. > > http://www.tug.org/mactex/SupportedSystems.html > > My Pismo PowerBook G3 still worked last year, and I assume it would still power up if I want to run Leopard very slowly. Hard to believe it’s nearly 20 years old. > > The major downside of dropping support for older versions is all the bullshit deprecation warnings, for which I blame iOS and Swift. They’ve really gotten out of hand, IMNSHO. > > — adam Unfortunately I also cannot make it work with libc++ and 10.6 dropped. I get a stupid warning about incompatible pointer types in FVCacheFile (even though there’s a clang diagnostic ignored), and more problematic, the new and delete don’t work in FVCacheFile. Any ideas? Christiaan |
From: Maxwell, A. R <Ada...@pn...> - 2018-10-31 17:30:41
|
> On Oct 31, 2018, at 10:05, Christiaan Hofman <cmh...@gm...> wrote: > > > I know exactly nothing about NSZone. I wonder how much the efficiency gains in fvzone are needed with newer OS versions. Last time I profiled it, it was still a decent performance win (Sierra, I think). NSZone is really optimized around tiny mallocs, for NSObject sizes rather than bitmap image sizes. Running FVAllocatorPerf on a 3.5 GHz Mac Pro with 10.13, I get: FVAllocator: 3.52 seconds for 20000 iterations CFAllocator: 6.21 seconds for 20000 iterations > I am glad I made a copy of Xcode 9 before updating to 10. But I probably will drop 10.6 anyway. That also solves my problem with ppc support that’s still there, and Sparkle does not check for architecture support (though I wonder if there’s even a single user for that, my last PPC machine died long ago). So dropping 10.6 will also ignore new releases for anyone using ppc, as that requires 10.6. BibDesk still had PPC support? I thought Xcode had dropped that years ago! FWIW, the MacTeX working group recently decided that MacTeX would officially support only versions of OS X for which Apple still provides security patches. Compiling, packaging, and testing had basically become impossible. http://www.tug.org/mactex/SupportedSystems.html My Pismo PowerBook G3 still worked last year, and I assume it would still power up if I want to run Leopard very slowly. Hard to believe it’s nearly 20 years old. The major downside of dropping support for older versions is all the bullshit deprecation warnings, for which I blame iOS and Swift. They’ve really gotten out of hand, IMNSHO. — adam |
From: Christiaan H. <cmh...@gm...> - 2018-10-31 17:05:40
|
> On 31 Oct 2018, at 17:46, Maxwell, Adam R <Ada...@pn...> wrote: > > >> On Oct 31, 2018, at 09:15, Christiaan Hofman <cmh...@gm...> wrote: >> >> Can the FileView project be rewritten without using c++, in particular for fvzone.cpp. Xcode 10.10 does not support libstdc++ anymore, and Mac OS X 10.6 does not have libc++. Unfortunately I do not understand much about what goes on in fvzone. > > In theory, it could be rewritten in C, but it wouldn’t be easy; since I wrote it a decade ago, I’d have to relearn the code myself. It’s conceptually simple, but you have to understand how malloc zones work, and that’s only documented in Apple’s source code. > > I ran into this yesterday with a new system that has 10.13 and Xcode 10 on it, and I’ll either drop 10.6 support or keep building TeX Live Utility with whatever older Xcode I have at home. I no longer have the time or energy to work around Apple’s SDK shortcomings, and replacing QTKit with AVFoundation was annoying enough. > > Since 10.6 hasn’t been updated since 2011, I don’t feel too bad about dropping support for it. I’m sure I’ll hear from the three people who still use it that their lives will be ruined if they have to keep using the prior version of my program along with an OS from a prior decade <eyeroll dot gif>. > > regards, > Adam I know exactly nothing about NSZone. I wonder how much the efficiency gains in fvzone are needed with newer OS versions. I am glad I made a copy of Xcode 9 before updating to 10. But I probably will drop 10.6 anyway. That also solves my problem with ppc support that’s still there, and Sparkle does not check for architecture support (though I wonder if there’s even a single user for that, my last PPC machine died long ago). So dropping 10.6 will also ignore new releases for anyone using ppc, as that requires 10.6. Christiaan |
From: Maxwell, A. R <Ada...@pn...> - 2018-10-31 16:46:39
|
> On Oct 31, 2018, at 09:15, Christiaan Hofman <cmh...@gm...> wrote: > > Can the FileView project be rewritten without using c++, in particular for fvzone.cpp. Xcode 10.10 does not support libstdc++ anymore, and Mac OS X 10.6 does not have libc++. Unfortunately I do not understand much about what goes on in fvzone. In theory, it could be rewritten in C, but it wouldn’t be easy; since I wrote it a decade ago, I’d have to relearn the code myself. It’s conceptually simple, but you have to understand how malloc zones work, and that’s only documented in Apple’s source code. I ran into this yesterday with a new system that has 10.13 and Xcode 10 on it, and I’ll either drop 10.6 support or keep building TeX Live Utility with whatever older Xcode I have at home. I no longer have the time or energy to work around Apple’s SDK shortcomings, and replacing QTKit with AVFoundation was annoying enough. Since 10.6 hasn’t been updated since 2011, I don’t feel too bad about dropping support for it. I’m sure I’ll hear from the three people who still use it that their lives will be ruined if they have to keep using the prior version of my program along with an OS from a prior decade <eyeroll dot gif>. regards, Adam |
From: Christiaan H. <cmh...@gm...> - 2018-10-31 16:15:28
|
Adam, Can the FileView project be rewritten without using c++, in particular for fvzone.cpp. Xcode 10.10 does not support libstdc++ anymore, and Mac OS X 10.6 does not have libc++. Unfortunately I do not understand much about what goes on in fvzone. Christiaan |