Right... well thats why i mention the 650 watt usage. thats one miner. Im gonna start small, and just go for enough power for one unit...
then work on the next one..and so on.
I think i figured it out enough to get 1 300ah batter, 3-200watt panels, and ofc a controller.
course, i wont know til i play with it, if thats really enough. oh and inverter ofc
that should be 3days at the 1500w level.
will ..eventually see how it goes.
g
Topic: [$XVG] VERGE [POW][MultiAlgo][TOR/i2P][no premine/ico!] - page 528. (Read 843883 times)
I've been trying to plan Solar power for my office. (i use the mining rigs for heat in winter)
i have to shut one rig down, eventually cuz its too hot. which means no scrypt
but im hoping to put up the panels asap...
I just have a hard time converting the Solar DC watt to AC watt...that i need lol.
ie: 650 watt full time rig... and a 1200watt rig... hm 1500watt would be smarter. (AC in summer/ scrypt in winter) lol.
is there a formulae for that? PM me that?
g
i have to shut one rig down, eventually cuz its too hot. which means no scrypt
but im hoping to put up the panels asap...
I just have a hard time converting the Solar DC watt to AC watt...that i need lol.
ie: 650 watt full time rig... and a 1200watt rig... hm 1500watt would be smarter. (AC in summer/ scrypt in winter) lol.
is there a formulae for that? PM me that?
g
it actually depends on what you want to do with it ... full dependance on solar means large solar capacity - as even the smaller miners use a huge amount of power ... where as hybrid solar / grid is another thing altogether ...
im currently working on a unique cooling system that may be be the answer to my issues ... as i dont just have one or two mahcines
...that project hasnt started yet - but it will ... so as long as i can mine ... i think verge will be on that horizon most of the time - along with granite and ozziecoin of course
... but massive changes are coming to them also in the coming weeks and months ...#crysx
I've been trying to plan Solar power for my office. (i use the mining rigs for heat in winter)
i have to shut one rig down, eventually cuz its too hot. which means no scrypt
but im hoping to put up the panels asap...
I just have a hard time converting the Solar DC watt to AC watt...that i need lol.
ie: 650 watt full time rig... and a 1200watt rig... hm 1500watt would be smarter. (AC in summer/ scrypt in winter) lol.
is there a formulae for that? PM me that?
g
i have to shut one rig down, eventually cuz its too hot. which means no scrypt
but im hoping to put up the panels asap...
I just have a hard time converting the Solar DC watt to AC watt...that i need lol.
ie: 650 watt full time rig... and a 1200watt rig... hm 1500watt would be smarter. (AC in summer/ scrypt in winter) lol.
is there a formulae for that? PM me that?
g
I'm always around...
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
hahaha ...
then you havent been bamboozled by the redhat team as yet ...
im a 'rhel guy' - and let me tell you that there is nothing that these guys would luv more than to add more 'red tape' ( pardon the red pun ) to their distro ... bloody fools ...
but its what i know - and im guessing its something to do with it ...
and before anyone suggests - NO! ... i wont go debian based ubuntu ... all my ststems are rhel based and i wont spend the next 2.5weeks reorganizing and redesigning the servers and workstations and especially thefarm ...
...will get to the bottom of it ...
just need to locate what it is thats missing from the compile structure that is causing this part to skip ... if in fact the qt part is processed at all ...
#crysx
if you see something that is fedora specific holding it back, feel free to make a pull request that fixes the build for fedora use on our repo. (just please make it fedora conditional, so it doesn't break the build, pull requests are auto-tested by travis-ci builder)
the very last lines after make it complete should tell you exactly what happened.
tanx ...
ill do what i can on my end - but possibly not tonight ( adelaide - south australia - australia ) ...
i appreciate all the help also guys ...
tanx ...
#crysx
Another Awesome Aussie !!
hahaha ...
you are a funny ( but also awesome ) guy ...
...#crysx
Live in beautiful downtown Busselton WA!!
i hear that western australia is a beautiful and HUGE place ... especially in perth and fremantle areas ...
ive visited a few times but havent stayed there long at any one time ... a friend of mine lives near the curtin university close to where she lives and she used to be an adelaide country girl ...
but ill be there soon by the looks of it ... you guys have a lot cheaper electricity off peak - and allow for better rates overall ... thefarm will luv it there i think
...#crysx
Yeah I live about 2 hrs south of perth/freo on the coast and when they were giving massive rebates on the solar power upgrades I went ball deep and pay $0 for power they actually pay me got that many panels on the roof cant tell what color my roof tiles are and rigs run like a fat kid running to the cake shot !! (and im not being mean I was that fat kid lol)
nice ...
so can i move thefarm into your living room then? ...
...will be so much warmer in winter ... hehehe ...
#crysx
Has the Windows version been released?
I see Linux and Mac.
I see Linux and Mac.
hi antonio ...
been a while mate ...
cant you compile windows versions? ...
im learning how to do it on windows - but would much prefer to cross compile via linux ...
need to learn how to do both - as i need this for my own coins also ... apparently windows compiles are WAY more complicated than any linux compiles ...
#crysx
I'm always around...
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
hahaha ...
then you havent been bamboozled by the redhat team as yet ...
im a 'rhel guy' - and let me tell you that there is nothing that these guys would luv more than to add more 'red tape' ( pardon the red pun ) to their distro ... bloody fools ...
but its what i know - and im guessing its something to do with it ...
and before anyone suggests - NO! ... i wont go debian based ubuntu ... all my ststems are rhel based and i wont spend the next 2.5weeks reorganizing and redesigning the servers and workstations and especially thefarm ...
...will get to the bottom of it ...
just need to locate what it is thats missing from the compile structure that is causing this part to skip ... if in fact the qt part is processed at all ...
#crysx
if you see something that is fedora specific holding it back, feel free to make a pull request that fixes the build for fedora use on our repo. (just please make it fedora conditional, so it doesn't break the build, pull requests are auto-tested by travis-ci builder)
the very last lines after make it complete should tell you exactly what happened.
tanx ...
ill do what i can on my end - but possibly not tonight ( adelaide - south australia - australia ) ...
i appreciate all the help also guys ...
tanx ...
#crysx
Another Awesome Aussie !!
hahaha ...
you are a funny ( but also awesome ) guy ...
...#crysx
Live in beautiful downtown Busselton WA!!
i hear that western australia is a beautiful and HUGE place ... especially in perth and fremantle areas ...
ive visited a few times but havent stayed there long at any one time ... a friend of mine lives near the curtin university close to where she lives and she used to be an adelaide country girl ...
but ill be there soon by the looks of it ... you guys have a lot cheaper electricity off peak - and allow for better rates overall ... thefarm will luv it there i think
...#crysx
Yeah I live about 2 hrs south of perth/freo on the coast and when they were giving massive rebates on the solar power upgrades I went ball deep and pay $0 for power they actually pay me got that many panels on the roof cant tell what color my roof tiles are and rigs run like a fat kid running to the cake shot !! (and im not being mean I was that fat kid lol)
ok ... so ...
now ./configure reports its happy with the dependencies it requires for the build - i notice its only qt4 that it picks up - instead of qt5 ...
i have both installed in fedora 23 x64 ( with fedora the command is qmake-qt4 / qmake-qt5 for project ( .pro ) files - and all dependencies are required for both qt versions ) - so the question remains - how can i force qt5 to be used? ... its not too much of an issue unless certain features cannot be displayed properly without qt5 - so ive compiled anyway ...
hey presto - VERGE-qt appears in the src/qt directory ...
installing it into the system ( yes - i have very meticulous procedures for this also ) and running it seems to be very smooth and i must admit - even with qt4 - its a nice looking wallet ...
syncing and working ...
i appreciate all your help guys ... so there is no need for any changes ( pull requests ) to the code - just a comment in the section of the readme to state that the 'other' development headers need to be installed also in the fedora 23 x64 / x32 distro ...
the protobuf-devel-2.6.1-2.fc23.x86_64 is NOT required with the compilation of those wallets that i have compiled here ( and there are many ) - as they usually come with a project ( .pro ) file in the root of the code ... though this is a very good lesson taught to watch out for in future for me ...
once again - tanx guys ...
#crysx
Code:
checking for SSL... yes
checking for CRYPTO... yes
checking for PROTOBUF... yes
checking for QR... yes
checking for protoc... /usr/bin/protoc
checking whether to build VERGEd... yes
checking for QT... yes
checking for QT_TEST... yes
checking for QT_DBUS... yes
checking for moc-qt4... /usr/bin/moc-qt4
checking for uic-qt4... /usr/bin/uic-qt4
checking for rcc-qt4... no
checking for rcc4... no
checking for rcc... /usr/bin/rcc
checking for lrelease-qt4... /usr/bin/lrelease-qt4
checking for lupdate-qt4... /usr/bin/lupdate-qt4
checking whether to build VERGE Core GUI... yes (Qt4)
checking if ccache should be used... yes
checking if wallet should be enabled... yes
checking for CRYPTO... yes
checking for PROTOBUF... yes
checking for QR... yes
checking for protoc... /usr/bin/protoc
checking whether to build VERGEd... yes
checking for QT... yes
checking for QT_TEST... yes
checking for QT_DBUS... yes
checking for moc-qt4... /usr/bin/moc-qt4
checking for uic-qt4... /usr/bin/uic-qt4
checking for rcc-qt4... no
checking for rcc4... no
checking for rcc... /usr/bin/rcc
checking for lrelease-qt4... /usr/bin/lrelease-qt4
checking for lupdate-qt4... /usr/bin/lupdate-qt4
checking whether to build VERGE Core GUI... yes (Qt4)
checking if ccache should be used... yes
checking if wallet should be enabled... yes
now ./configure reports its happy with the dependencies it requires for the build - i notice its only qt4 that it picks up - instead of qt5 ...
i have both installed in fedora 23 x64 ( with fedora the command is qmake-qt4 / qmake-qt5 for project ( .pro ) files - and all dependencies are required for both qt versions ) - so the question remains - how can i force qt5 to be used? ... its not too much of an issue unless certain features cannot be displayed properly without qt5 - so ive compiled anyway ...
hey presto - VERGE-qt appears in the src/qt directory ...
installing it into the system ( yes - i have very meticulous procedures for this also ) and running it seems to be very smooth and i must admit - even with qt4 - its a nice looking wallet ...
syncing and working ...
i appreciate all your help guys ... so there is no need for any changes ( pull requests ) to the code - just a comment in the section of the readme to state that the 'other' development headers need to be installed also in the fedora 23 x64 / x32 distro ...
the protobuf-devel-2.6.1-2.fc23.x86_64 is NOT required with the compilation of those wallets that i have compiled here ( and there are many ) - as they usually come with a project ( .pro ) file in the root of the code ... though this is a very good lesson taught to watch out for in future for me ...
once again - tanx guys ...
#crysx
If both qt4 and qt5 are installed, qt4 will be used by default.
./configure --with-gui=qt5
Should force it to use qt5
tanx again mate ...
ill try that out now ...
#crysx
I'm always around...
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
hahaha ...
then you havent been bamboozled by the redhat team as yet ...
im a 'rhel guy' - and let me tell you that there is nothing that these guys would luv more than to add more 'red tape' ( pardon the red pun ) to their distro ... bloody fools ...
but its what i know - and im guessing its something to do with it ...
and before anyone suggests - NO! ... i wont go debian based ubuntu ... all my ststems are rhel based and i wont spend the next 2.5weeks reorganizing and redesigning the servers and workstations and especially thefarm ...
...will get to the bottom of it ...
just need to locate what it is thats missing from the compile structure that is causing this part to skip ... if in fact the qt part is processed at all ...
#crysx
if you see something that is fedora specific holding it back, feel free to make a pull request that fixes the build for fedora use on our repo. (just please make it fedora conditional, so it doesn't break the build, pull requests are auto-tested by travis-ci builder)
the very last lines after make it complete should tell you exactly what happened.
tanx ...
ill do what i can on my end - but possibly not tonight ( adelaide - south australia - australia ) ...
i appreciate all the help also guys ...
tanx ...
#crysx
Another Awesome Aussie !!
hahaha ...
you are a funny ( but also awesome ) guy ...
...#crysx
Live in beautiful downtown Busselton WA!!
i hear that western australia is a beautiful and HUGE place ... especially in perth and fremantle areas ...
ive visited a few times but havent stayed there long at any one time ... a friend of mine lives near the curtin university close to where she lives and she used to be an adelaide country girl ...
but ill be there soon by the looks of it ... you guys have a lot cheaper electricity off peak - and allow for better rates overall ... thefarm will luv it there i think
...#crysx
Has the Windows version been released?
I see Linux and Mac.
hasnt been announced yet.I see Linux and Mac.
(woot, quote worked that time!)
g
Has the Windows version been released?
I see Linux and Mac.
I see Linux and Mac.
ok ... so ...
now ./configure reports its happy with the dependencies it requires for the build - i notice its only qt4 that it picks up - instead of qt5 ...
i have both installed in fedora 23 x64 ( with fedora the command is qmake-qt4 / qmake-qt5 for project ( .pro ) files - and all dependencies are required for both qt versions ) - so the question remains - how can i force qt5 to be used? ... its not too much of an issue unless certain features cannot be displayed properly without qt5 - so ive compiled anyway ...
hey presto - VERGE-qt appears in the src/qt directory ...
installing it into the system ( yes - i have very meticulous procedures for this also ) and running it seems to be very smooth and i must admit - even with qt4 - its a nice looking wallet ...
syncing and working ...
i appreciate all your help guys ... so there is no need for any changes ( pull requests ) to the code - just a comment in the section of the readme to state that the 'other' development headers need to be installed also in the fedora 23 x64 / x32 distro ...
the protobuf-devel-2.6.1-2.fc23.x86_64 is NOT required with the compilation of those wallets that i have compiled here ( and there are many ) - as they usually come with a project ( .pro ) file in the root of the code ... though this is a very good lesson taught to watch out for in future for me ...
once again - tanx guys ...
#crysx
Code:
checking for SSL... yes
checking for CRYPTO... yes
checking for PROTOBUF... yes
checking for QR... yes
checking for protoc... /usr/bin/protoc
checking whether to build VERGEd... yes
checking for QT... yes
checking for QT_TEST... yes
checking for QT_DBUS... yes
checking for moc-qt4... /usr/bin/moc-qt4
checking for uic-qt4... /usr/bin/uic-qt4
checking for rcc-qt4... no
checking for rcc4... no
checking for rcc... /usr/bin/rcc
checking for lrelease-qt4... /usr/bin/lrelease-qt4
checking for lupdate-qt4... /usr/bin/lupdate-qt4
checking whether to build VERGE Core GUI... yes (Qt4)
checking if ccache should be used... yes
checking if wallet should be enabled... yes
now ./configure reports its happy with the dependencies it requires for the build - i notice its only qt4 that it picks up - instead of qt5 ...
i have both installed in fedora 23 x64 ( with fedora the command is qmake-qt4 / qmake-qt5 for project ( .pro ) files - and all dependencies are required for both qt versions ) - so the question remains - how can i force qt5 to be used? ... its not too much of an issue unless certain features cannot be displayed properly without qt5 - so ive compiled anyway ...
hey presto - VERGE-qt appears in the src/qt directory ...
installing it into the system ( yes - i have very meticulous procedures for this also ) and running it seems to be very smooth and i must admit - even with qt4 - its a nice looking wallet ...
syncing and working ...
i appreciate all your help guys ... so there is no need for any changes ( pull requests ) to the code - just a comment in the section of the readme to state that the 'other' development headers need to be installed also in the fedora 23 x64 / x32 distro ...
the protobuf-devel-2.6.1-2.fc23.x86_64 is NOT required with the compilation of those wallets that i have compiled here ( and there are many ) - as they usually come with a project ( .pro ) file in the root of the code ... though this is a very good lesson taught to watch out for in future for me ...
once again - tanx guys ...
#crysx
If both qt4 and qt5 are installed, qt4 will be used by default.
./configure --with-gui=qt5
Should force it to use qt5
I'm always around...
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
hahaha ...
then you havent been bamboozled by the redhat team as yet ...
im a 'rhel guy' - and let me tell you that there is nothing that these guys would luv more than to add more 'red tape' ( pardon the red pun ) to their distro ... bloody fools ...
but its what i know - and im guessing its something to do with it ...
and before anyone suggests - NO! ... i wont go debian based ubuntu ... all my ststems are rhel based and i wont spend the next 2.5weeks reorganizing and redesigning the servers and workstations and especially thefarm ...
...will get to the bottom of it ...
just need to locate what it is thats missing from the compile structure that is causing this part to skip ... if in fact the qt part is processed at all ...
#crysx
if you see something that is fedora specific holding it back, feel free to make a pull request that fixes the build for fedora use on our repo. (just please make it fedora conditional, so it doesn't break the build, pull requests are auto-tested by travis-ci builder)
the very last lines after make it complete should tell you exactly what happened.
tanx ...
ill do what i can on my end - but possibly not tonight ( adelaide - south australia - australia ) ...
i appreciate all the help also guys ...
tanx ...
#crysx
Another Awesome Aussie !!
hahaha ...
you are a funny ( but also awesome ) guy ...
...#crysx
Live in beautiful downtown Busselton WA!!
I'm always around...
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
hahaha ...
then you havent been bamboozled by the redhat team as yet ...
im a 'rhel guy' - and let me tell you that there is nothing that these guys would luv more than to add more 'red tape' ( pardon the red pun ) to their distro ... bloody fools ...
but its what i know - and im guessing its something to do with it ...
and before anyone suggests - NO! ... i wont go debian based ubuntu ... all my ststems are rhel based and i wont spend the next 2.5weeks reorganizing and redesigning the servers and workstations and especially thefarm ...
...will get to the bottom of it ...
just need to locate what it is thats missing from the compile structure that is causing this part to skip ... if in fact the qt part is processed at all ...
#crysx
if you see something that is fedora specific holding it back, feel free to make a pull request that fixes the build for fedora use on our repo. (just please make it fedora conditional, so it doesn't break the build, pull requests are auto-tested by travis-ci builder)
the very last lines after make it complete should tell you exactly what happened.
tanx ...
ill do what i can on my end - but possibly not tonight ( adelaide - south australia - australia ) ...
i appreciate all the help also guys ...
tanx ...
#crysx
Another Awesome Aussie !!
hahaha ...
you are a funny ( but also awesome ) guy ...
...#crysx
ok ... so ...
now ./configure reports its happy with the dependencies it requires for the build - i notice its only qt4 that it picks up - instead of qt5 ...
i have both installed in fedora 23 x64 ( with fedora the command is qmake-qt4 / qmake-qt5 for project ( .pro ) files - and all dependencies are required for both qt versions ) - so the question remains - how can i force qt5 to be used? ... its not too much of an issue unless certain features cannot be displayed properly without qt5 - so ive compiled anyway ...
hey presto - VERGE-qt appears in the src/qt directory ...
installing it into the system ( yes - i have very meticulous procedures for this also ) and running it seems to be very smooth and i must admit - even with qt4 - its a nice looking wallet ...
syncing and working ...
i appreciate all your help guys ... so there is no need for any changes ( pull requests ) to the code - just a comment in the section of the readme to state that the 'other' development headers need to be installed also in the fedora 23 x64 / x32 distro ...
the protobuf-devel-2.6.1-2.fc23.x86_64 is NOT required with the compilation of those wallets that i have compiled here ( and there are many ) - as they usually come with a project ( .pro ) file in the root of the code ... though this is a very good lesson taught to watch out for in future for me ...
once again - tanx guys ...
#crysx
Code:
checking for SSL... yes
checking for CRYPTO... yes
checking for PROTOBUF... yes
checking for QR... yes
checking for protoc... /usr/bin/protoc
checking whether to build VERGEd... yes
checking for QT... yes
checking for QT_TEST... yes
checking for QT_DBUS... yes
checking for moc-qt4... /usr/bin/moc-qt4
checking for uic-qt4... /usr/bin/uic-qt4
checking for rcc-qt4... no
checking for rcc4... no
checking for rcc... /usr/bin/rcc
checking for lrelease-qt4... /usr/bin/lrelease-qt4
checking for lupdate-qt4... /usr/bin/lupdate-qt4
checking whether to build VERGE Core GUI... yes (Qt4)
checking if ccache should be used... yes
checking if wallet should be enabled... yes
now ./configure reports its happy with the dependencies it requires for the build - i notice its only qt4 that it picks up - instead of qt5 ...
i have both installed in fedora 23 x64 ( with fedora the command is qmake-qt4 / qmake-qt5 for project ( .pro ) files - and all dependencies are required for both qt versions ) - so the question remains - how can i force qt5 to be used? ... its not too much of an issue unless certain features cannot be displayed properly without qt5 - so ive compiled anyway ...
hey presto - VERGE-qt appears in the src/qt directory ...
installing it into the system ( yes - i have very meticulous procedures for this also ) and running it seems to be very smooth and i must admit - even with qt4 - its a nice looking wallet ...
syncing and working ...
i appreciate all your help guys ... so there is no need for any changes ( pull requests ) to the code - just a comment in the section of the readme to state that the 'other' development headers need to be installed also in the fedora 23 x64 / x32 distro ...
the protobuf-devel-2.6.1-2.fc23.x86_64 is NOT required with the compilation of those wallets that i have compiled here ( and there are many ) - as they usually come with a project ( .pro ) file in the root of the code ... though this is a very good lesson taught to watch out for in future for me ...
once again - tanx guys ...
#crysx
I'm always around...
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
hahaha ...
then you havent been bamboozled by the redhat team as yet ...
im a 'rhel guy' - and let me tell you that there is nothing that these guys would luv more than to add more 'red tape' ( pardon the red pun ) to their distro ... bloody fools ...
but its what i know - and im guessing its something to do with it ...
and before anyone suggests - NO! ... i wont go debian based ubuntu ... all my ststems are rhel based and i wont spend the next 2.5weeks reorganizing and redesigning the servers and workstations and especially thefarm ...
...will get to the bottom of it ...
just need to locate what it is thats missing from the compile structure that is causing this part to skip ... if in fact the qt part is processed at all ...
#crysx
if you see something that is fedora specific holding it back, feel free to make a pull request that fixes the build for fedora use on our repo. (just please make it fedora conditional, so it doesn't break the build, pull requests are auto-tested by travis-ci builder)
the very last lines after make it complete should tell you exactly what happened.
tanx ...
ill do what i can on my end - but possibly not tonight ( adelaide - south australia - australia ) ...
i appreciate all the help also guys ...
tanx ...
#crysx
Another Awesome Aussie !!
hehehe ...
guess what ive found ... ill try and rectify this soon ...
event though its installed - its the x64 version ... should the x32 version be installed also? ...
tanx guys ...
edit - wait up ... i just realized i dont have the protobuf development headers installed ... installing now and will post results ...
#crysx
guess what ive found ... ill try and rectify this soon ...
Code:
checking for SSL... yes
checking for CRYPTO... yes
checking for PROTOBUF... no
configure: WARNING: libprotobuf not found; bitcoin-qt frontend will not be built
checking whether to build VERGEd... yes
checking whether to build VERGE Core GUI... no (Qt)
event though its installed - its the x64 version ... should the x32 version be installed also? ...
tanx guys ...
edit - wait up ... i just realized i dont have the protobuf development headers installed ... installing now and will post results ...
#crysx
I'm always around...
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
hahaha ...
then you havent been bamboozled by the redhat team as yet ...
im a 'rhel guy' - and let me tell you that there is nothing that these guys would luv more than to add more 'red tape' ( pardon the red pun ) to their distro ... bloody fools ...
but its what i know - and im guessing its something to do with it ...
and before anyone suggests - NO! ... i wont go debian based ubuntu ... all my ststems are rhel based and i wont spend the next 2.5weeks reorganizing and redesigning the servers and workstations and especially thefarm ...
...will get to the bottom of it ...
just need to locate what it is thats missing from the compile structure that is causing this part to skip ... if in fact the qt part is processed at all ...
#crysx
if you see something that is fedora specific holding it back, feel free to make a pull request that fixes the build for fedora use on our repo. (just please make it fedora conditional, so it doesn't break the build, pull requests are auto-tested by travis-ci builder)
the very last lines after make it complete should tell you exactly what happened.
tanx ...
ill do what i can on my end - but possibly not tonight ( adelaide - south australia - australia ) ...
i appreciate all the help also guys ...
tanx ...
#crysx
I'm always around...
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
hahaha ...
then you havent been bamboozled by the redhat team as yet ...
im a 'rhel guy' - and let me tell you that there is nothing that these guys would luv more than to add more 'red tape' ( pardon the red pun ) to their distro ... bloody fools ...
but its what i know - and im guessing its something to do with it ...
and before anyone suggests - NO! ... i wont go debian based ubuntu ... all my ststems are rhel based and i wont spend the next 2.5weeks reorganizing and redesigning the servers and workstations and especially thefarm ...
...will get to the bottom of it ...
just need to locate what it is thats missing from the compile structure that is causing this part to skip ... if in fact the qt part is processed at all ...
#crysx
if you see something that is fedora specific holding it back, feel free to make a pull request that fixes the build for fedora use on our repo. (just please make it fedora conditional, so it doesn't break the build, pull requests are auto-tested by travis-ci builder)
the very last lines after make it complete should tell you exactly what happened.
I'm always around...
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
Anyways, the build process with autotools is quite verbose in its output, it won't just silently fail to do something
hahaha ...
then you havent been bamboozled by the redhat team as yet ...
im a 'rhel guy' - and let me tell you that there is nothing that these guys would luv more than to add more 'red tape' ( pardon the red pun ) to their distro ... bloody fools ...
but its what i know - and im guessing its something to do with it ...
and before anyone suggests - NO! ... i wont go debian based ubuntu ... all my ststems are rhel based and i wont spend the next 2.5weeks reorganizing and redesigning the servers and workstations and especially thefarm ...
...will get to the bottom of it ...
just need to locate what it is thats missing from the compile structure that is causing this part to skip ... if in fact the qt part is processed at all ...
#crysx
hi all ...
what are the procedures ( and no im not a newbie in compiling - i just am a little lost at the moment with the source ) to compile a qt wallet in fedora 23 x64 ...
i see no form of .pro file to compile from ...
a brief outline would be very helpful ...
tanx in advance ...
#crysx
what are the procedures ( and no im not a newbie in compiling - i just am a little lost at the moment with the source ) to compile a qt wallet in fedora 23 x64 ...
i see no form of .pro file to compile from ...
a brief outline would be very helpful ...
tanx in advance ...
#crysx
you should be able to install the dependencies (as listed in the readme) and then run the compile commands (./autogen.sh && ./configure && make)
yes - and the daemon compiled nicely ... tanx ...
but the qt wallet is what im after ...
there seems to be no project file in the source for me to build ...
so i was wondering where ( or moreover - how ) a qt wallet can be compiled here ... if at all ...
if qt is NOT part of the compilation procedure - how would i compile a gui wallet from the source ...
#crysx
it didnt create a VERGE-qt in the /src/qt directory like it says it does on the readme?
nup - it didnt mate ...
though the compile went through flawlessly - there is no verge qt file in there ...
#crysx
are you sure? if the compile went flawlessly, then you have a VERGE-qt file in your /verge/src/qt folder. (not the /src/ folder where the daemon VERGEd is)
yes - i am sure ...
please dont let this newbie account fool you - i am having issues with my account ( hero almost legendary - chrysophylax profile ) that the bct people are taking their time to look at and reset so i can get my profile back ...
i know how to compile and have been doing for a long time now ... for other wallets as well as my own coins ...
this one is stumping me ... it is NOT pushing a qt wallet into the directory where it should - and it seems the daemon is the only thing it is creating ...
cloned the git - and compiled ... VERGEd but no VERGE-qt wallet ...
i can use it as a daemon anyway - but i prefer to have the pretty pictures and looks of the wallet
...ill clean the compile and start over again - and see what it does this time ... ill also keep an eye out for the suggestion fuzzbawls made with the ./configure output and see if anything looks awry ...
but i can guarantee - that if it compiled the daemon - then there is something else happening here thats stopping the qt wallet ...
ill try in a few minutes ...
#crysx
Jump to: