Topic: [DVC]DevCoin - Official Thread - Moderated - page 243. (Read 1059181 times)

Where is 1.0.12 available from anyways? Is that the one that's on Devcoin.org now (under wallet -> Windows -> Windows Installer)?

you can use my node, just change settings-> trusted peer to "d.evco.in", and restart the wallet.

This is a bit too technical for me. I think I can manage if you elaborate on this.

c++ gcc runtimes although i prob need them anyways for the base src. I will build it and create a new version to test.

Yea I guess but running multiple daemons at once prob makes sense to have dynamic linking.. even for qt better to just do the same since its in the same dir.

What do you mean runtime libs?

To build a coin you need all the -devel packages from your distro for all the libs it depends on, if you want static libs for some distro things you also need maybe not jsut the -devel package but also a package containing specifically static libs, not all -devel packages even contain the static libs maybe. (Not sure if that applies specifically to the current set of dependencies bitcoin-derived coins have or not though, just in general some packages have a -static separate from the -dev or -devel package.)

Mind you there are security reasons for insisting on static libs when distributing binaries.

I am concerned with when the users are going to do their own compiling, because in that case the static libs that came from their distro system are as easily caused to be corrupt as the dynamic libs that came from their distro system so no security advantage to making them use the static ones.

I think bitcoin's makefile.unix makes some things static moostly because the creators of the makefile planned to use it themselves to make binaries for distribution.

Maybe it should have a make distro separate from a make bitcoind or something like that so the special case of making binaries to distribute doesn't spoil the dynamicness of when you make binaries for your own use. Or just not default to assuming everyone is normally making binaries to distribute but rather that they are normally making binaries to execute.

-MarkM-

Ok I will change it to link dynamically. But the libs them selves will be statically built to avoid putting in runtime libs sound fair?

I left other makefiles alone expect a dev to fix and give me the updated file for each os.

I hope so. It gets tiresome having to meddle with the makefiles of all the coin daemons to make sure they all use dynamic linking.

Especially for merged mined coins it makes sense to assume people will run many of the daemons.

-MarkM-

EDIT: P.S. dll ? Ouch. I don't care what crap windows people use just don't make the makefile.unix for the daemon force everything to static.

dlls for windows have always been a shocking horror story. Linux type distros though tend to do dynamic libs rather well.

Hi Weckel,

Nothing strange I see? Its doing version check with devcoin nodes 32500 and 32400 and severing connection?

You need to point to your new wallet node. Run new wallet 1.0.12 on your computer and set your internet ip address in your android wallet settings and say in there to skip normal peer activity select the checkbox.

You should connect to it and stay connected.

The Android wallet is showing strange behaviour: http://www.youtube.com/watch?v=52KO2UBsDEs

It does not seem to update the block chain properly. Can you look into this before I try to pay some coins into this wallet?

My issue with sharing code is that software changes and breaks compatibility so since coins have their own repos and developers things change amd invalidate commonalities.. I would rather not be involved in debugging a problem that ends up being because the other executablr used a different version of libcurl that doesnt have multithreading enabled. Each of thr dependant libs can be built with different options and changes the code so sharing across coins is probably asking for trouble.

Only ram it takes is loading it on execution versus demand.. I dont see it as a problem its 40 megs on startup looks ok to me.

The original memory problem you refer to should be fixed because I included the changed rsnel made to serealize auxpow blocks to disk in cdiskblockheader instead of memory only.

I think devcoin needs something else added to it... it should be used for something else, bitcoin has gambling sites, black markets, and is widely accepted as a currency both online and not online. Devcoin is really not all that much though. We should get more online things to accept devcoin if we want the value to rise. I think (if I am allowed) more bounties should go out to people that want to make more devcoin accepted businesses. Lets say I am just some random person that thinks the ethical idea is cool, why would I buy a ton of them if they really can not be spent on a ton of things? I know this message may have a bad sound to it but I really think that more bounties must be offered for more businesses if we want the value to rise and if we want more people to accept this coin. I love devcoin and I think this would be in its best interests for growth.
Thanks,
-AM

no, not any magic that will detect libs static linked into other binarys. the only advantage is redistributing easily and professionally.

Yes Mark you're right, no need to distributed devcoind static, because all those people using devcoind will be sys admins, that they are not likely to use directly binarys and will prefer to build themselves. I think sidhujag may refer to devcoin-qt linux version, instead of devcoind.

Doesn't static waste a huge amount of RAM? At least if lots of coins all are static doesn't that stop them sharing code pages for all the libs they all have in common?

We still haven't gotten the RAM hogging fix into all the merged mined coins and already people want to start making them hog more for libs they all use?

Or is there some smarts in the sharing that will notice the static libs are the same and share them?

-MarkM-

yes that's d.evco.in:52333, you can always use this because that's my vps server and it's up more than 99% of the time.

I'll try to compile all the dependency static.... though I think the best way is to use automake/autoconf buiding system, which bitcoin 0.8.6 already does.

http://forum.devcoin.org

Will now point to coinzen. Hyperspire can you update the site to add a link to the forum when you get a chance ?

Its better to be static so we send out a single file... the reason you are not able to run with static is cause
one of the dependencies were not compiled statically. With db boost
openssl etc you need to compile these with static aswell and then use the static libs in the makefile.. the executable grows in size too but its better. once you do this can you send me linux executable I will put it in installer..

Yea the android only connects to new nodes for security reasons im sure it would work but there are loopholes that would open up.

so can i point to your node aswell then? d.evco.in:52333?

I went thru quite a bit of pain to ensure I can link everything statically.. although there are some boost performance gains using dynamic linking its really a tradeoff and to me more professional to have it static.

If you have trouble let me know I will give you commands on how to conpile the dependencies statically. Infact I will update the readme.

They don't block this one...

http://www.moneyandpotatoes.com/freelance-writer-earn-some-extra-money-with-devtome/


It probably ended up being a little long and confusing but it could get people interested. The social buttons are at the bottom of the article.

well you can't say anything on "FB" because the content nazis immediately block any devtome.com or devcoin.org address......

newest wallet(devcoind on linux x32) and android wallet(1.0.1) tested, basically it all works like a charm, great work! I tested the new windows version of qt gui, sending receiving via qr code from and to android wallet, everything works.

and some minor issues:

1. devcoind need to be compiled dynamically, i'd manually removed the '--static' flag. If not, the compilation finished but it report "cannot find file or directory" while starting devcoind;

2. I suppose the android wallet does not compatible with old devcoin nodes yet? because it cannot connect to any peer, so I let it point to my own node which has deployed the newest devcoind (d.evco.in with default port), and it works.

What do you mean by signature ad campaign? Is my faucet doing that? https://bitcointalksearch.org/topic/m.1983573