[ANN][NMC] Namecoin Wallet (QT) with integrated Name Registration v3.75

[bluebelt]

what does this mean and what do i need to compile namecoin-qt ?  help, please!
--------------------------------------------
$ make
g++ -c -O2 -Wno-invalid-offsetof -Wformat -DNOPCH -DFOURWAYSSE2 -DUSE_SSL  -DBOOST_THREAD_USE_LIB -I../libs/openssl-1.0.1e/include -I../libs/db-4.7.25.NC/build_unix -I../libs/boost_1_50_0 -o obj/nogui/auxpow.o auxpow.cpp
In file included from auxpow.cpp:4:0:
headers.h:63:29: fatal error：boost/foreach.hpp：no such file or directory
stop.
make: *** [obj/nogui/auxpow.o] error 1
-------------------------------------------

... looks like you might have unsatisfied dependencies. Check this page for some help.

http://dot-bit.org/BuildNamecoinQTFromSource

More precisely here, it's the boost library headers you're missing.

thanks you very much!

 i run 'slapt-get --search'ed and installed  boost  package  ,  after this, make step work for a while then show a lot errors 

Code:

../src/serialize.h:400:5:   required from ‘void Unserialize(Stream&, T&, long int, int) [with Stream = CDataStream; T = CTxIn]’
../src/serialize.h:522:13:   required from ‘void Unserialize_impl(Stream&, std::vector<T, A>&, int, int, const false_type&) [with Stream = CDataStream; T = CTxIn; A = std::allocator<CTxIn>; boost::false_type = boost::integral_constant<bool, false>]’
../src/serialize.h:529:5：
../src/serialize.h:741:5:   required from ‘unsigned int SerReadWrite(Stream&, T&, int, int, CSerActionUnserialize) [with Stream = CDataStream; T = CMerkleTx]’
../src/wallet.h:390:5:   required from ‘void CWalletTx::Unserialize(Stream&, int, int) [with Stream = CDataStream]’
../src/serialize.h:400:5:   required from ‘void Unserialize(Stream&, T&, long int, int) [with Stream = CDataStream; T = CWalletTx]’
../src/serialize.h:1056:9:   required from ‘CDataStream& CDataStream::operator>>(T&) [with T = CWalletTx; CDataStream = CDataStream]’
../src/db.h:77:9:   required from ‘bool CDB::Read(const K&, T&) [with K = std::pair<std::basic_string<char>, uint256>; T = CWalletTx]’
../src/walletdb.h:33:65:   required from here
../src/main.h:250:5: warning：unused-variable‘fGetSize’ [-Wunused-variable]
../src/main.h:250:5: warning：unused-variable‘fWrite’ [-Wunused-variable]
../src/main.h:250:5: warning：unused-variable‘fRead’ [-Wunused-variable]
In file included from ../src/util.cpp:6:0:
/usr/include/boost/program_options/detail/config_file.hpp: In instantiation of ‘bool boost::program_options::detail::basic_config_file_iterator<charT>::getline(std::string&) [with charT = char; std::string = std::basic_string<char>]’:
../src/util.cpp:1103:1:   required from here
/usr/include/boost/program_options/detail/config_file.hpp:163:13: error：‘to_internal’ was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive]
In file included from /usr/include/boost/program_options/detail/parsers.hpp:9:0,
                 from /usr/include/boost/program_options/parsers.hpp:265,
                 from ../src/util.cpp:7:
/usr/include/boost/program_options/detail/convert.hpp:75:34:  ：‘template<class T> std::vector<std::basic_string<char> > boost::program_options::to_internal(const std::vector<T>&)’ declared here, later in the translation unit
../src/util.cpp:972:41: error：  warn_unused_result  ‘size_t fwrite(const void*, size_t, size_t, FILE*)’  [-Wunused-result]
In file included from ../src/script.h:8:0,
                 from ../src/main.h:10,
                 from ../src/headers.h:100,
                 from ../src/util.cpp:4:
../src/keystore.h:  ‘virtual bool CKeyStore::HaveKey(const std::vector<unsigned char>&) const’中:
../src/keystore.h:60:5: error：  [-Wreturn-type]
make: *** [build/util.o] error 1

help please.

[lanfeusst]

Code:

qmake "USE_UPNP=-"

Like it's explained in
http://dot-bit.org/BuildNamecoinQTFromSource

[snailbrain]

New Namecoin EasyWinBuilder version here: https://github.com/phelixnmc/namecoin-qt

It is creating a disassembly hash of Namecoin-Qt, please let me know if you get the same hash
(see https://bitcointalk.org/index.php?topic=252931.msg2766894#msg2766894)


Also it includes a patch that made downloading of the blockchain 8 times faster on a hard disk based system (tested for the first 20,000blocks). Also it's not thrashing the disk any more and is generally more responsive. 

Please review and tell me if you consider my changes safe (they are all stolen from Bitcoin). I think the main problem was repeatedly flushing some databases to disk.

Note that I have not tested this intensively yet. Backup your wallets!

I downloaded the whole blockchain in a little less than 1.5 hours (ssd, i3, -dbcache=1500). So I will call this v3.64GT 
Other than this there are no changes to Snailbrain's v3.64.

If you get a hard system crash (blue screen of death) it may be slightly more likely be necessary to redownload the blockchain. Your wallet should be as safe as before.

Test with care and backup your wallet

Sources: https://github.com/phelixnmc/namecoin-qt

Beta Windows binary release: http://blockchained.com/stuff/namecoin-qt-winbin-0.3.64gt.zip
sha256: 89a3040ff30b42ee3bc271661affd7cadf9f7b97853e74bf8798432830b16e7d

Windows Users:

I would very much appreciate if somebody could rebuild and verify the disassembly hash and thus the validity of my binary file/hash / zip hash:

Code:

Hash of Qt binary [experimental]...
File hash sha256:
3e821775c7fd9a52e28a62bae37cfb2459e5d9eb110e7d244908f86dfd4cae2a *../release/nam
ecoin-qt.exe

Hash sha256 of disassembly [may take a while]:
a2b3ca0dd00a3b95ee4772379336e963ebbe2341d69ba1839739893a5edd5c80  -

phelix got: a2b3ca0dd00a3b95ee4772379336e963ebbe2341d69ba1839739893a5edd5c80

How to do it:
1.) Download the .zip file on github
2.) run __all_easywinbuilder.bat and follow instructions  (you will need to install MinGW and Qt manually!)
3.) wait for downloading, unpacking of dependencies and for building of Namecoin daemon and Namecoin Qt
4.) The scripts will come up with hashes like above. Post them here.
5.) Download my binaries and unpack.
6.) Open a command line, cd to the easywinbuilder directory
7.) run: dahash pathtotheunpackedbinaries\namecoin-qt.exe
8.) Post the output here (hopefully the disassembly hash will match).
9.) Verify the hash of the zip file
 open freshly installed MinGW shell
 cd /driveletter/yourpathtothezipfile
 shasum -a 256 namecoin-qt-winbin-0.3.64gt.zip
10.) Check that the dlls in the zip are the same as the ones in your release directory

You have then verified that my binaries are built from the github files without modification.
People then will not have to trust me alone for the binaries.

edited

thanks Phelix.. will add your commit with next update ... or do you want to put requests in to the namecoin-qt repo (with folder tidy ups)? .. otherwise things are going to get muddled up for khal to pull into official repo?

[phelix]

New Namecoin EasyWinBuilder version here: https://github.com/phelixnmc/namecoin-qt

It is creating a disassembly hash of Namecoin-Qt, please let me know if you get the same hash
(see https://bitcointalk.org/index.php?topic=252931.msg2766894#msg2766894)


Also it includes a patch that made downloading of the blockchain 8 times faster on a hard disk based system (tested for the first 20,000blocks). Also it's not thrashing the disk any more and is generally more responsive. 

Please review and tell me if you consider my changes safe (they are all stolen from Bitcoin). I think the main problem was repeatedly flushing some databases to disk.

Note that I have not tested this intensively yet. Backup your wallets!

I downloaded the whole blockchain in a little less than 1.5 hours (ssd, i3, -dbcache=1500). So I will call this v3.64GT 
Other than this there are no changes to Snailbrain's v3.64.

If you get a hard system crash (blue screen of death) it may be slightly more likely be necessary to redownload the blockchain. Your wallet should be as safe as before.

Test with care and backup your wallet

Sources: https://github.com/phelixnmc/namecoin-qt

Beta Windows binary release: http://blockchained.com/stuff/namecoin-qt-winbin-0.3.64gt.zip
sha256: 89a3040ff30b42ee3bc271661affd7cadf9f7b97853e74bf8798432830b16e7d

Windows Users:

I would very much appreciate if somebody could rebuild and verify the disassembly hash and thus the validity of my binary file/hash / zip hash:

Code:

Hash of Qt binary [experimental]...
File hash sha256:
3e821775c7fd9a52e28a62bae37cfb2459e5d9eb110e7d244908f86dfd4cae2a *../release/nam
ecoin-qt.exe

Hash sha256 of disassembly [may take a while]:
a2b3ca0dd00a3b95ee4772379336e963ebbe2341d69ba1839739893a5edd5c80  -

phelix got: a2b3ca0dd00a3b95ee4772379336e963ebbe2341d69ba1839739893a5edd5c80

How to do it:
1.) Download the .zip file on github
2.) run __all_easywinbuilder.bat and follow instructions  (you will need to install MinGW and Qt manually!)
3.) wait for downloading, unpacking of dependencies and for building of Namecoin daemon and Namecoin Qt
4.) The scripts will come up with hashes like above. Post them here.
5.) Download my binaries and unpack.
6.) Open a command line, cd to the easywinbuilder directory
7.) run: dahash pathtotheunpackedbinaries\namecoin-qt.exe
8.) Post the output here (hopefully the disassembly hash will match).
9.) Verify the hash of the zip file
 open freshly installed MinGW shell
 cd /driveletter/yourpathtothezipfile
 shasum -a 256 namecoin-qt-winbin-0.3.64gt.zip
10.) Check that the dlls in the zip are the same as the ones in your release directory

You have then verified that my binaries are built from the github files without modification.
People then will not have to trust me alone for the binaries.

edited

thanks Phelix.. will add your commit with next update ... or do you want to put requests in to the namecoin-qt repo (with folder tidy ups)? .. otherwise things are going to get muddled up for khal to pull into official repo?

I will create pull requests, hoping you can agree to the folder changes. I was hoping for more testing....


btw: https://bitcointalk.org/index.php?topic=262219.0   vote for NMC/USD  on BTC-e

[Atheros]

I followed the directions here: http://dot-bit.org/BuildNamecoinQTFromSource

On this step:

qmake "USE_UPNP=-"

I get these errors:

Project MESSAGE: Building without UPNP support
Project MESSAGE: Building without IPv6 support
sh: 1: /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease: not found
WARNING: Failure to find: auxpow.cpp
WARNING: Failure to find: headers.h
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_bg.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_ca_ES.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_cs.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_da.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_de.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_el_GR.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_en.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_es.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_es_CL.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_et.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_eu_ES.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_fa.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_fa_IR.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_fi.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_fr.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_fr_CA.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_he.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_hr.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_hu.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_it.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_lt.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_nb.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_nl.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_pl.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_pt_BR.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_pt_PT.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_ro_RO.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_ru.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_sk.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_sr.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_sv.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_tr.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_uk.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_zh_CN.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_zh_TW.qm'

I also tried using QT Creator and the namecoin-qt.pro file but that gave me an error about auxpow.cpp. I'd like to use Namecoin for something but if I can't get it to work then my users certainly won't be able to.

[marcus_of_augustus]

I followed the directions here: http://dot-bit.org/BuildNamecoinQTFromSource

On this step:

qmake "USE_UPNP=-"

I get these errors:

Project MESSAGE: Building without UPNP support
Project MESSAGE: Building without IPv6 support
sh: 1: /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease: not found
WARNING: Failure to find: auxpow.cpp
WARNING: Failure to find: headers.h
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_bg.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_ca_ES.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_cs.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_da.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_de.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_el_GR.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_en.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_es.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_es_CL.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_et.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_eu_ES.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_fa.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_fa_IR.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_fi.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_fr.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_fr_CA.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_he.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_hr.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_hu.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_it.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_lt.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_nb.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_nl.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_pl.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_pt_BR.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_pt_PT.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_ro_RO.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_ru.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_sk.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_sr.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_sv.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_tr.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_uk.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_zh_CN.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_zh_TW.qm'

I also tried using QT Creator and the namecoin-qt.pro file but that gave me an error about auxpow.cpp. I'd like to use Namecoin for something but if I can't get it to work then my users certainly won't be able to.

Which source are you using? What OS? Any other info that you think might be helpful.

Edit: I just tried it out here and didn't see anything like that ... seems to be saying some source/header files not found?

[phelix]

I followed the directions here: http://dot-bit.org/BuildNamecoinQTFromSource

On this step:

qmake "USE_UPNP=-"

I get these errors:

Project MESSAGE: Building without UPNP support
Project MESSAGE: Building without IPv6 support
sh: 1: /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease: not found
WARNING: Failure to find: auxpow.cpp
WARNING: Failure to find: headers.h
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_bg.qm'
[...]

I also tried using QT Creator and the namecoin-qt.pro file but that gave me an error about auxpow.cpp. I'd like to use Namecoin for something but if I can't get it to work then my users certainly won't be able to.

Which source are you using? What OS? Any other info that you think might be helpful.

Edit: I just tried it out here and didn't see anything like that ... seems to be saying some source/header files not found?

Looks like some path is missing / incorrect.

[markm]

I finally managed to compile this.

The vast spew of warnings had obscured the actual cause of the error, which was simply the lack of tolerance for out of order definations or templates or whatever. The compiler actually pretty much tells you what flag/switch to use to make it not insist on presumably newer stricter rules about templates or definitions being out of order / not appearing before being used or somesuch. I cannot recall the actual word they use that basically means be more lenient.

I also haven't actually fired it up yet as I don't actually use GUIs. I just wanted a more recent version of the daemon than what I had been using.

many older coins need the lenience thing, usually I notice it, but I compiled via "screen" so have no scrollback buffer and this thing spews so many warnings I initially figured I'd need to try again with more scrollback to go back far enough to find the actual error. Which might actually be how I found it this time or maybe it really was burried in the pageful I could see but I just hadn't picked it out from among all the warnings the first time.

Maybe it would be useful for the automess ./configure for coins that need that leniency thing to check what version of compiler you are using and add that flag if your compiler is recent enough to have it.

Ah I recall the word now: permissive. It needs permissive mode.

-MarkM-

[phelix]

I finally managed to compile this.

The vast s;ew of warnings had obscured the actual cause of the error, which was simply the lack of tolerance for out of order definations or templates or whatever. The compiler actually pretty much tells you what flag/switch to use to make it not insist on presumably newer stricter rules about templates or definitions being out of order / not appearing before being used or somesuch. I cannot recall the actual word they use that basically means be more lenient.

I also haven't actually fired it up yet as I don't actually use GUIs. I just wanted a more recent version of the daemon than what I had been using.

many older coins need the lenience thing, usually I notice it, but I compiled via "screen" so have no scrollback buffer and this thing spews so many warnings I initially figured I'd need to try again with more scrollback to go back far enough to find the actual error. Which might actually be how I found it this time or maybe it really was burried in the pageful I could see but I just hadn't picked it out from among all the warnings the first time.

Maybe it would be useful for the automess ./configure for coins that need that leniency thing to check what version of compiler you are using and add that flag if your compiler is recent enough to have it.

Ah I recall the word now: permissive. It needs permissive mode.

-MarkM-

I guess you are on Linux?

Here are some flags to get rid of most of the horrible mass of warnings:
 -Wno-unused-variable -Wno-unused-value -Wno-sign-compare -Wno-strict-aliasing

Unfortunately we could not clean up the code even if we had the time to do so because we need to stick to Bitcoin as close as possible...

[Atheros]

Which source are you using? What OS? Any other info that you think might be helpful.

Edit: I just tried it out here and didn't see anything like that ... seems to be saying some source/header files not found?

I'm on Xubuntu 13.04. I am using the most recent Namecoin code (in the namecoin-qt branch) as of now. Here is the latest entry from 'git log':

Merge: c540853 a9c69f2
Author: khalahan <khal@dot-bit.org>
Date:   Mon Jul 1 12:11:55 2013 +0200

    Merge branch 'namecoin-qt-snailbrain' into namecoin-qt

Thank you.

[marcus_of_augustus]

Which source are you using? What OS? Any other info that you think might be helpful.

Edit: I just tried it out here and didn't see anything like that ... seems to be saying some source/header files not found?

I'm on Xubuntu 13.04. I am using the most recent Namecoin code (in the namecoin-qt branch) as of now. Here is the latest entry from 'git log':

Merge: c540853 a9c69f2
Author: khalahan <khal@dot-bit.org>
Date:   Mon Jul 1 12:11:55 2013 +0200

    Merge branch 'namecoin-qt-snailbrain' into namecoin-qt

Thank you.

snailbrain ^^ ??

PS : as I said previously, I suggest your coder puts namecoin-qt.pro in the top dir  (not project) and stops using all those "../" paths since you do not know how different OS and qmake versions will interpret that on all possible platforms ... or simply put, just follow the bitcoin-qt dir/build structure.

[phelix]

Which source are you using? What OS? Any other info that you think might be helpful.

Edit: I just tried it out here and didn't see anything like that ... seems to be saying some source/header files not found?

I'm on Xubuntu 13.04. I am using the most recent Namecoin code (in the namecoin-qt branch) as of now. Here is the latest entry from 'git log':

Merge: c540853 a9c69f2
Author: khalahan <khal@dot-bit.org>
Date:   Mon Jul 1 12:11:55 2013 +0200

    Merge branch 'namecoin-qt-snailbrain' into namecoin-qt

Thank you.

snailbrain ^^ ??

PS : as I said previously, I suggest your coder puts namecoin-qt.pro in the top dir  (not project) and stops using all those "../" paths since you do not know how different OS and qmake versions will interpret that on all possible platforms ... or simply put, just follow the bitcoin-qt dir/build structure.

I have created a pull request that does that. It also includes the easywinbuilder directory but you can simply delete it if you don't want it to be included.

[phelix]

horrible job explaining what it is etc.
you just launch into a long winded techno-ramble..

when a user opens the page they wanna know what is going on not that json validation is enabled for example,

Fork and improve!


So.... are we ready for an official release / release candidate? If not what needs to be done?

[virtualmaster]

The actual version seems to be stable enough and has a lot of new improvements also thanks to snailbrain.
Wouldn't be possible to implement an id/ lookup in the new client ? May be more people would use the id system.

[bucktotal]

So.... are we ready for an official release / release candidate? If not what needs to be done?

i would like to continue donating to the development fund, do you agree that the links in the OP are still the best place to send some funds?

[phelix]

So.... are we ready for an official release / release candidate? If not what needs to be done?

i would like to continue donating to the development fund, do you agree that the links in the OP are still the best place to send some funds?

Yes, Snailbrain has done great work for the good cause.

[phelix]

It seems it is not possible to only do a name_new via the GUI? I clicked cancel on the firstupdate screen but it did the firstupdates anyway on the next start...

If I click "cancel" on the initial firstupdate screen it should do nothing.

[snailbrain]

It seems it is not possible to only do a name_new via the GUI? I clicked cancel on the firstupdate screen but it did the firstupdates anyway on the next start...

If I click "cancel" on the initial firstupdate screen it should do nothing.

it will do it.. but you can use console if you wanted to do a name_new and not do a firtstupdate, but why?

[snailbrain]

So.... are we ready for an official release / release candidate? If not what needs to be done?

i would like to continue donating to the development fund, do you agree that the links in the OP are still the best place to send some funds?

We are still working on official release at the moment (a few technicalities )

as for donations, if it's for the work (and ongoing) on the qt any donations would be greatly appreciated..

if it's for namecoin projects in general you should use donation http://namecoin.info/
if there is a particular namecoin project you like you can donate directly to them.. (I won't list a load of names incase i forget someone)

[phelix]

It seems it is not possible to only do a name_new via the GUI? I clicked cancel on the firstupdate screen but it did the firstupdates anyway on the next start...

If I click "cancel" on the initial firstupdate screen it should do nothing.

it will do it.. but you can use console if you wanted to do a name_new and not do a firtstupdate, but why?

This is quite unexpected. Maybe I want to do the name_firstupdate at a certain point in time?

Also if I enter data into the configure screen the first time it pops up will it then always do a third name_op?  name_new, name_firstupdate with default data, name_update with my data?

The point is maybe i would like to time the name_firstupdate to a certain point in time to sync it with normal domain registration for example. I think this is quite an important point.