sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
April 25, 2014, 07:38:05 AM |
|
Looking at this makefile... why on earth are you building libcurl? It's on quite a few linux systems. The user is supposed to install the dependencies, except sometimes in the case of Windows...
Because you cant assume users have it.. unless you do a dynamic compile then its up to you to put the dll as a registered dll or in path of executable. Take a look at the config for the build.. Then windows mingw makefile atleast. It strips out everything except the http get functionality. Also it needs to be statically linked because I believe it is safer and avoids bugs where multi-threading could cause issues.. I believe this is why they went with the static build for it.. was done before me.
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
April 25, 2014, 11:36:37 AM |
|
Looking at this makefile... why on earth are you building libcurl? It's on quite a few linux systems. The user is supposed to install the dependencies, except sometimes in the case of Windows...
Because you cant assume users have it.. unless you do a dynamic compile then its up to you to put the dll as a registered dll or in path of executable. Take a look at the config for the build.. Then windows mingw makefile atleast. It strips out everything except the http get functionality. Also it needs to be statically linked because I believe it is safer and avoids bugs where multi-threading could cause issues.. I believe this is why they went with the static build for it.. was done before me. You're thinking like a Windows user. If you're compiling for Linux, there is no reason to compile libcurl with Devcoin. If all developers thought like you, it'd be a disaster. Shared libraries were created so that every program didn't have to statically link their own copy of a common library, wasting memory and disk space. Several distros don't ship static binaries, and AFAIK, it won't cause issues unless you're using archaic versions. I believe I did change the dependencies to be dynamically linked and included them in the distro. With libcurl it the lib is compiled without the unneeded options so that is why the src was included. It wasnt a standard lib that any coins used at the time so the src was put in the repo. You still need the src to compile the linked lib and since we are only using 1/10th of it having src there makes sense.
|
|
|
|
emfox
|
|
April 25, 2014, 02:20:59 PM |
|
Looking at this makefile... why on earth are you building libcurl? It's on quite a few linux systems. The user is supposed to install the dependencies, except sometimes in the case of Windows...
Because you cant assume users have it.. unless you do a dynamic compile then its up to you to put the dll as a registered dll or in path of executable. Take a look at the config for the build.. Then windows mingw makefile atleast. It strips out everything except the http get functionality. Also it needs to be statically linked because I believe it is safer and avoids bugs where multi-threading could cause issues.. I believe this is why they went with the static build for it.. was done before me. You're thinking like a Windows user. If you're compiling for Linux, there is no reason to compile libcurl with Devcoin. If all developers thought like you, it'd be a disaster. Shared libraries were created so that every program didn't have to statically link their own copy of a common library, wasting memory and disk space. Several distros don't ship static binaries, and AFAIK, it won't cause issues unless you're using archaic versions. I believe I did change the dependencies to be dynamically linked and included them in the distro. With libcurl it the lib is compiled without the unneeded options so that is why the src was included. It wasnt a standard lib that any coins used at the time so the src was put in the repo. You still need the src to compile the linked lib and since we are only using 1/10th of it having src there makes sense. How does it make sense to only waste a little memory copying code that already should be on the system? And what if there's a security bug in libcurl? With dynamic linking, I can use my package manager to upgrade. This way, I need to recompile EVERYTHING that depends on it. Hello wolf. As the current linux admin of devcoin, I tell you just go ahead, to adapt the build method of linux as you like, and ask sidhujag to pull it. Because he is of the responsibility of developing our new release, but not the release manager of every distribution (though he happened to be maintaining the windows build). I was not too familiar with those libcurl hacks, and a little too busy to dig into it, so just modify the code (of linux part) as you like. I think sidhujag would like to see it, too, right?
|
Earn Devcoins by WritingBTC: 1Emfox1WswYcd2YucUskRzqfRWKkcm1Jut DVC: 1Emfox1WswYcd2YucUskRzqfRWKkcm1Jut IXC: xnRKo3qSDdcPJ4pgTLER3orkquUVQXeLwf
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
April 25, 2014, 06:01:56 PM |
|
Thanks, it makes sense for linux. We only know about the libcurl issues with windows so it can be a specific thing for the win mingw file.
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
April 26, 2014, 03:26:23 PM |
|
Thanks, it makes sense for linux. We only know about the libcurl issues with windows so it can be a specific thing for the win mingw file. No problem. Like I said, I might do a bit more work on it later. The following looks wrong to me: test check: test_bitcoin FORCE ./test_bitcoin
Lines 149-150 in my repo. Thanks.. since you seem interested would you like to do the unit tests for devcoin? it is a good way to help you understand exactly what the code does. Most of the bitcoin tests should be valid and we would need some for merge mining (from namecoin?) and share stuff which libcurl is used for. Its been a nagging thing I wanted to get to but didnt have time. If you dont want to do that another thing that needs to be done is the build scripts that allow the node to be built across the platforms on the cloud. We can fund the hosting and base it per build (when code changes) again bitcoin already has this but our makefiles need to be all working then we can do the same thing.
|
|
|
|
MoreGuney
Newbie
Offline
Activity: 21
Merit: 0
|
|
April 26, 2014, 04:33:51 PM |
|
Hello. I was hoping someone could assist / advise. I've head some devcoins (~100K) in my wallet but haven't added any in at least six months. So I open the wallet, it doesn't sync, so I do the usual - delete the devcoin wallet folder, delete the devcoin associated files in appdata/roaming (EXCEPT the WALLET.DAT, of course,) download the new version and run it.....after it 'synced' (it DOES list all the previous transactions, all the blocks, etc. But they are all GRAYED OUT and my balance is 0. Can anyone assist with this issue? Many thanks in advance!
|
|
|
|
MoreGuney
Newbie
Offline
Activity: 21
Merit: 0
|
|
April 26, 2014, 06:35:05 PM |
|
Hello. I was hoping someone could assist / advise. I've head some devcoins (~100K) in my wallet but haven't added any in at least six months. So I open the wallet, it doesn't sync, so I do the usual - delete the devcoin wallet folder, delete the devcoin associated files in appdata/roaming (EXCEPT the WALLET.DAT, of course,) download the new version and run it.....after it 'synced' (it DOES list all the previous transactions, all the blocks, etc. But they are all GRAYED OUT and my balance is 0. Can anyone assist with this issue? Many thanks in advance! Wait for it to sync. I have. Still says "0". Oh, and "WARNING: Displayed transactions may not be correct". Is all lost? Thanks again.
|
|
|
|
MoreGuney
Newbie
Offline
Activity: 21
Merit: 0
|
|
April 27, 2014, 12:26:52 AM |
|
Hello. I was hoping someone could assist / advise. I've head some devcoins (~100K) in my wallet but haven't added any in at least six months. So I open the wallet, it doesn't sync, so I do the usual - delete the devcoin wallet folder, delete the devcoin associated files in appdata/roaming (EXCEPT the WALLET.DAT, of course,) download the new version and run it.....after it 'synced' (it DOES list all the previous transactions, all the blocks, etc. But they are all GRAYED OUT and my balance is 0. Can anyone assist with this issue? Many thanks in advance! Wait for it to sync. I have. Still says "0". Oh, and "WARNING: Displayed transactions may not be correct". Is all lost? Thanks again. Most likely, your wallet installation is fucked, but your coins are fine as long as the wallet.dat is intact. If you can get the private keys, you can spend your coins. Thank you very much for the information. I downloaded the Devcoin-WindowsBundle. Should I try something else? Thanks again.
|
|
|
|
|
btcjason3
Newbie
Offline
Activity: 2
Merit: 0
|
|
April 27, 2014, 03:17:21 AM |
|
It's clear that devcoin will be a coin for the long term.
|
|
|
|
ranlo
Legendary
Offline
Activity: 1988
Merit: 1007
|
|
April 27, 2014, 03:58:36 AM |
|
Hey guys, RapidBalls now has a jackpot of 202235 DVC, along with the chance to win 5000x your bet! Jackpot is still growing but nobody has taken it yet.
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
April 27, 2014, 07:23:49 AM |
|
If you dont want to do that another thing that needs to be done is the build scripts that allow the node to be built across the platforms on the cloud. We can fund the hosting and base it per build (when code changes) again bitcoin already has this but our makefiles need to be all working then we can do the same thing.
What exactly do you need the build scripts modified to do? I would like devcoin to be built the same way as bitcoin. If it uses cloud then it probably downloads all the dependencies and makes everything.. im not sure exactly what the bitcoin build system is like but it does make all the different platforms as now we have seperate admins responsible for the builds it would be ideal if we can automate this process.
|
|
|
|
weisoq
|
|
April 27, 2014, 09:53:10 AM |
|
Fixed.
Cool, although still seems to be stalling on a past date.
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
April 27, 2014, 05:27:17 PM |
|
If you dont want to do that another thing that needs to be done is the build scripts that allow the node to be built across the platforms on the cloud. We can fund the hosting and base it per build (when code changes) again bitcoin already has this but our makefiles need to be all working then we can do the same thing.
What exactly do you need the build scripts modified to do? I would like devcoin to be built the same way as bitcoin. If it uses cloud then it probably downloads all the dependencies and makes everything.. im not sure exactly what the bitcoin build system is like but it does make all the different platforms as now we have seperate admins responsible for the builds it would be ideal if we can automate this process. Oh god, you want to use autotools. Its essentially the start of a real release process which we dont have: https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.mdUsing the gitian builder procedure is like this https://github.com/bitcoin/bitcoin/blob/master/doc/gitian-building.md scripts are already in btc src directory.
|
|
|
|
emfox
|
|
April 28, 2014, 12:12:55 PM |
|
If you dont want to do that another thing that needs to be done is the build scripts that allow the node to be built across the platforms on the cloud. We can fund the hosting and base it per build (when code changes) again bitcoin already has this but our makefiles need to be all working then we can do the same thing.
What exactly do you need the build scripts modified to do? I would like devcoin to be built the same way as bitcoin. If it uses cloud then it probably downloads all the dependencies and makes everything.. im not sure exactly what the bitcoin build system is like but it does make all the different platforms as now we have seperate admins responsible for the builds it would be ideal if we can automate this process. Oh god, you want to use autotools. Its essentially the start of a real release process which we dont have: https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.mdUsing the gitian builder procedure is like this https://github.com/bitcoin/bitcoin/blob/master/doc/gitian-building.md scripts are already in btc src directory. I like the autotools when I'm building a project, but as a developer, I hate them. I tried to learn it several times, the documentation SUUUUUCKS. Me too. but truely, If we want to follow bitcoin, we should consider using autotools, that bitcoin has already did in 0.8.6 (or may be 0.8.7?)
|
Earn Devcoins by WritingBTC: 1Emfox1WswYcd2YucUskRzqfRWKkcm1Jut DVC: 1Emfox1WswYcd2YucUskRzqfRWKkcm1Jut IXC: xnRKo3qSDdcPJ4pgTLER3orkquUVQXeLwf
|
|
|
bronan
|
|
April 28, 2014, 07:34:27 PM |
|
I have the program open for an hour and no connections are made How dead can a coin be last update on the program freaking aug 2013 no changes no news so how can you say it has a future if clearly hardly anybody takes it serious
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
April 28, 2014, 08:49:47 PM |
|
I have the program open for an hour and no connections are made How dead can a coin be last update on the program freaking aug 2013 no changes no news so how can you say it has a future if clearly hardly anybody takes it serious
checkout devcoinauctions.com... dead? sure lol... There is a new wallet being tested right now. Maybe you are using a different client, where did you download from?
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
April 28, 2014, 08:51:48 PM |
|
If you dont want to do that another thing that needs to be done is the build scripts that allow the node to be built across the platforms on the cloud. We can fund the hosting and base it per build (when code changes) again bitcoin already has this but our makefiles need to be all working then we can do the same thing.
What exactly do you need the build scripts modified to do? I would like devcoin to be built the same way as bitcoin. If it uses cloud then it probably downloads all the dependencies and makes everything.. im not sure exactly what the bitcoin build system is like but it does make all the different platforms as now we have seperate admins responsible for the builds it would be ideal if we can automate this process. Oh god, you want to use autotools. Its essentially the start of a real release process which we dont have: https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.mdUsing the gitian builder procedure is like this https://github.com/bitcoin/bitcoin/blob/master/doc/gitian-building.md scripts are already in btc src directory. I like the autotools when I'm building a project, but as a developer, I hate them. I tried to learn it several times, the documentation SUUUUUCKS. It is alot better than when I was writing the new client... and its the reason why I didn't bother because overly complicated and not documented. But it is getting better now and doable based on the docs I read anyway. Just the MacOSX will have to be built on something other than debian.
|
|
|
|
a20756079
|
|
April 28, 2014, 10:12:30 PM |
|
It is getting a bit confusing with the changes of the Devcoin thread. Hope that the trolls will leave us alone.
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
April 28, 2014, 11:47:32 PM |
|
It is getting a bit confusing with the changes of the Devcoin thread. Hope that the trolls will leave us alone.
We are now on coinzen.org... it has a troll detector
|
|
|
|
|