[00:58:42] <navcoin-bot> <dy5es41> anyone have any ideas as to why our unix build is failing here?  error log travis (https://travis-ci.org/NAVCoin/navcoin-core/jobs/499564490): qt_navcoin_qt_SOURCES += qt/macdockiconhandler.mm qt/macnotificationhandler.mm /bin/bash: qt_navcoin_qt_SOURCES: command not found make[1]: *** [qt/moc_addressbookpage.cpp] Error 127 make[1]: Leaving directory `/home/travis/build/NAVCoin/navcoin-core/build/src' make: *** [src/qt/navcoin-qt]
[00:58:43] <navcoin-bot> Error 2  error log aguycalled:  qt_navcoin_qt_SOURCES += qt/macdockiconhandler.mm qt/macnotificationhandler.mm make[2]: qt_navcoin_qt_SOURCES: No such file or directory make[2]: *** [qt/moc_communityfundpage.cpp] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1  make keeps interpreting qt_navcoin_qt_SOURCES as either a directory/binary and cannot find it (it's not defined as a variable) even though it is defined here
[00:58:43] <navcoin-bot> in src/qt/Makefile.qt.include:  473 qt_navcoin_qt_SOURCES = qt/navcoin.cpp 474 if TARGET_DARWIN 475   qt_navcoin_qt_SOURCES += $(NAVCOIN_MM) 476 endif 477 if TARGET_WINDOWS 478   qt_navcoin_qt_SOURCES += $(NAVCOIN_RC)
[01:08:19] <navcoin-bot> <mc290> you mean your mac builds?
[01:08:52] <navcoin-bot> <Hayden> Yes
[01:09:10] <navcoin-bot> <dy5es41> is macos unix
[01:09:13] <navcoin-bot> <dy5es41> ?
[01:09:34] <navcoin-bot> <dy5es41> i mean macos 😃
[02:27:23] <navcoin-bot> <Hayden> @aguycalled We have it building on travis now, if you want to try build it whenever you have time
[12:53:35] *** Quits: navcoin-bot (~navcoin-b@nav.community) (Remote host closed the connection)
[12:53:49] *** Joins: navcoin-bot (~navcoin-b@nav.community)
[22:26:56] <navcoin-bot> <aguycalled> osx building works for me now btw
[22:32:44] <navcoin-bot> <aguycalled> some comments, i think it would be more convenient if the community fund tab filtered by pending by default
[22:32:59] <navcoin-bot> <aguycalled> https://cdn.discordapp.com/attachments/416000318149754881/550807654956793868/unknown.png
[22:33:18] <navcoin-bot> <aguycalled> ^ those two fields in proposal details read a bit confusing
[22:33:28] <navcoin-bot> <aguycalled> i would maybe label the second as Voting period finishes in:
[22:40:05] <navcoin-bot> <dy5es41> sweet
[22:41:09] <navcoin-bot> <mc290> how about the first as "Proposal duration:"?
[22:41:28] <navcoin-bot> <aguycalled> yep
[22:41:50] <navcoin-bot> <aguycalled> but still the second is not completely accurate, as the proposal appears as rejected if not accepted after the voting ends iirc
[22:41:59] <navcoin-bot> <mc290> yeah true
[22:53:37] <navcoin-bot> <Matt (Dev)> Deadline should be something like Proposal Duration I agree