Hello,
My name is Fernando Nakagawa and I’m continuing the work that Leandro
Boscariol made last year as a part of my master graduation. Well, I saw that
avogadro has modified a lot since then, so I’m working on porting his code
to make avogadro runs, but I’m having some problems here. It seems that it
compiles, but when linking it give me some errors. Somebody have any idea
what it could be?
Nice to meet you all!
Fernando Nakagawa
On Tuesday 18 August 2009 17:36:17 Fernando Nakagawa wrote:
Hello,
My name is Fernando Nakagawa and I’m continuing the work that Leandro
Boscariol made last year as a part of my master graduation. Well, I saw
that avogadro has modified a lot since then, so I’m working on porting his
code to make avogadro runs, but I’m having some problems here. It seems
that it compiles, but when linking it give me some errors. Somebody have
any idea what it could be?Nice to meet you all!
Fernando Nakagawa
It looks like you are using an old version of Avogadro, or have stale plugins
around. The plugins no longer use the lib prefix - so it would be
forcefieldextension.so. Did you checkout the latest sources using git? See the
instructions below,
http://avogadro.openmolecules.net/wiki/Compiling_on_Linux_and_Mac_OS_X
http://avogadro.openmolecules.net/wiki/Working_With_Git
If you have trouble then please let me know.
Thanks,
Marcus
Hey there!
Well, actually I’m trying to add an extension to avogadro, so maybe that’s
the reason it threw those problems. But I’m still having some trouble. At
first I added planeconstraintdialog.cpp, planeconstraintdialog.h and
planeconstraintdialog.ui in the same extensions directory. I made some
modifications to forcefielextension.cpp and forcefieldextension.h (as far as
I know the plane constraint dialog that Leandro created belongs to force
field extension) and to CMakeLists.txt.
I guess it’s the CMakeLists.txt, because when I change it, different errors
occur. I also dont know how to use the CMakeLists correctly, is there something I can read to know more about it? In annex are the files I have added and modified. In CMakeLists the trouble is on "Molecular Mechanics force fields". I hope its a silly problem.
Thanks for helping!
Fernando Nakagawa
On Tue, Aug 18, 2009 at 8:46 PM, Marcus D. Hanwell marcus@cryos.org wrote:
On Tuesday 18 August 2009 17:36:17 Fernando Nakagawa wrote:
Hello,
My name is Fernando Nakagawa and I’m continuing the work that Leandro
Boscariol made last year as a part of my master graduation. Well, I saw
that avogadro has modified a lot since then, so I’m working on porting
his
code to make avogadro runs, but I’m having some problems here. It seems
that it compiles, but when linking it give me some errors. Somebody have
any idea what it could be?Nice to meet you all!
Fernando Nakagawa
It looks like you are using an old version of Avogadro, or have stale
plugins
around. The plugins no longer use the lib prefix - so it would be
forcefieldextension.so. Did you checkout the latest sources using git? See
the
instructions below,http://avogadro.openmolecules.net/wiki/Compiling_on_Linux_and_Mac_OS_X
http://avogadro.openmolecules.net/wiki/Working_With_GitIf you have trouble then please let me know.
Thanks,
Marcus
Ahh the error that was thrown is:
make[2]: *** Sem regra para processar o alvo ../libavogadro/src/extensions/ planeconstraintdialog.ui', necessário por libavogadro/src/extensions/ui_
planeconstraintdialog.h’. Pare.
make[1]: **
[libavogadro/src/extensions/CMakeFiles/forcefieldextension.dir/all] Erro 2
make: ** [all] Erro 2
*** Sem regra para processar o alvo = no rule to make target
Fernando Nakagawa
On Fri, Aug 21, 2009 at 11:32 AM, Fernando Nakagawa naka86@gmail.comwrote:
Hey there!
Well, actually I’m trying to add an extension to avogadro, so maybe that’s
the reason it threw those problems. But I’m still having some trouble. At
first I added planeconstraintdialog.cpp, planeconstraintdialog.h and
planeconstraintdialog.ui in the same extensions directory. I made some
modifications to forcefielextension.cpp and forcefieldextension.h (as far as
I know the plane constraint dialog that Leandro created belongs to force
field extension) and to CMakeLists.txt.
I guess it’s the CMakeLists.txt, because when I change it, different errors
occur. I also dont know how to use the CMakeLists correctly, is there something I can read to know more about it? In annex are the files I have added and modified. In CMakeLists the trouble is on "Molecular Mechanics force fields". I hope its a silly problem.Thanks for helping!
Fernando Nakagawa
On Tue, Aug 18, 2009 at 8:46 PM, Marcus D. Hanwell marcus@cryos.orgwrote:
On Tuesday 18 August 2009 17:36:17 Fernando Nakagawa wrote:
Hello,
My name is Fernando Nakagawa and I’m continuing the work that Leandro
Boscariol made last year as a part of my master graduation. Well, I saw
that avogadro has modified a lot since then, so I’m working on porting
his
code to make avogadro runs, but I’m having some problems here. It seems
that it compiles, but when linking it give me some errors. Somebody have
any idea what it could be?Nice to meet you all!
Fernando Nakagawa
It looks like you are using an old version of Avogadro, or have stale
plugins
around. The plugins no longer use the lib prefix - so it would be
forcefieldextension.so. Did you checkout the latest sources using git? See
the
instructions below,http://avogadro.openmolecules.net/wiki/Compiling_on_Linux_and_Mac_OS_X
http://avogadro.openmolecules.net/wiki/Working_With_GitIf you have trouble then please let me know.
Thanks,
Marcus
On Fri, Aug 21, 2009 at 5:33 PM, Fernando Nakagawanaka86@gmail.com wrote:
Ahh the error that was thrown is:
make[2]: *** Sem regra para processar o alvo
../libavogadro/src/extensions/ planeconstraintdialog.ui', necessário porlibavogadro/src/extensions/ui_
planeconstraintdialog.h’. Pare.
make[1]: **
[libavogadro/src/extensions/CMakeFiles/forcefieldextension.dir/all] Erro 2
make: ** [all] Erro 2*** Sem regra para processar o alvo = no rule to make target
Fernando Nakagawa
It seems like the white space is causing the problems:
`…/libavogadro/src/extensions/ planeconstraintdialog.ui’
In the CMakeLists.txt file, make sure to remove all (there is only
one) spaces in “forcefielddialog.ui;constraintsdialog.ui;conformersearchdialog.ui;
planeconstraintdialog.ui”
CMakeLists.txt are part of the cmake build system. There is
documentation available on www.cmake.org or just google cmake.
Tim
On Fri, Aug 21, 2009 at 11:32 AM, Fernando Nakagawa naka86@gmail.com
wrote:Hey there!
Well, actually I’m trying to add an extension to avogadro, so maybe that’s
the reason it threw those problems. But I’m still having some trouble. At
first I added planeconstraintdialog.cpp, planeconstraintdialog.h and
planeconstraintdialog.ui in the same extensions directory. I made some
modifications to forcefielextension.cpp and forcefieldextension.h (as far as
I know the plane constraint dialog that Leandro created belongs to force
field extension) and to CMakeLists.txt.
I guess it’s the CMakeLists.txt, because when I change it, different
errors occur. I also dont know how to use the CMakeLists correctly, is there something I can read to know more about it? In annex are the files I have added and modified. In CMakeLists the trouble is on "Molecular Mechanics force fields". I hope its a silly
problem.Thanks for helping!
Fernando Nakagawa
On Tue, Aug 18, 2009 at 8:46 PM, Marcus D. Hanwell marcus@cryos.org
wrote:On Tuesday 18 August 2009 17:36:17 Fernando Nakagawa wrote:
Hello,
My name is Fernando Nakagawa and I’m continuing the work that Leandro
Boscariol made last year as a part of my master graduation. Well, I saw
that avogadro has modified a lot since then, so I’m working on porting
his
code to make avogadro runs, but I’m having some problems here. It seems
that it compiles, but when linking it give me some errors. Somebody
have
any idea what it could be?Nice to meet you all!
Fernando Nakagawa
It looks like you are using an old version of Avogadro, or have stale
plugins
around. The plugins no longer use the lib prefix - so it would be
forcefieldextension.so. Did you checkout the latest sources using git?
See the
instructions below,http://avogadro.openmolecules.net/wiki/Compiling_on_Linux_and_Mac_OS_X
http://avogadro.openmolecules.net/wiki/Working_With_GitIf you have trouble then please let me know.
Thanks,
Marcus
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus
on
what you do best, core application coding. Discover what’s new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
avogadro-devel List Signup and Options
Hi guys!
After that silly problem, I`m still having trouble. I hope to be useful
after knowing how to get rid of these problems, and not to be disturbing
right now.
Well… somebody have a clue for this?
Linking CXX shared module …/…/…/lib/forcefieldextension.so
CMakeFiles/forcefieldextension.dir/moc_planeconstraintdialog.cxx.o: In
function Avogadro::PlaneConstraintDialog::metaObject() const': moc_planeconstraintdialog.cxx:(.text+0x0): multiple definition of Avogadro::PlaneConstraintDialog::metaObject() const’
CMakeFiles/forcefieldextension.dir/planeconstraintdialog.cpp.o:planeconstraintdialog.cpp:(.text+0x10):
first defined here
CMakeFiles/forcefieldextension.dir/moc_planeconstraintdialog.cxx.o:(.
data.rel.ro+0x0): multiple definition of
Avogadro::PlaneConstraintDialog::staticMetaObject' CMakeFiles/forcefieldextension.dir/planeconstraintdialog.cpp.o:(.data.rel.ro+0x0): first defined here CMakeFiles/forcefieldextension.dir/moc_planeconstraintdialog.cxx.o: In function Avogadro::PlaneConstraintDialog::qt_metacall(QMetaObject::Call,
int, void**)‘:
moc_planeconstraintdialog.cxx:(.text+0x70): multiple definition of
Avogadro::PlaneConstraintDialog::qt_metacall(QMetaObject::Call, int, void**)' CMakeFiles/forcefieldextension.dir/planeconstraintdialog.cpp.o:planeconstraintdialog.cpp:(.text+0x8b0): first defined here CMakeFiles/forcefieldextension.dir/moc_planeconstraintdialog.cxx.o: In function Avogadro::PlaneConstraintDialog::qt_metacast(char const*)’:
moc_planeconstraintdialog.cxx:(.text+0xe0): multiple definition of
`Avogadro::PlaneConstraintDialog::qt_metacast(char const*)’
CMakeFiles/forcefieldextension.dir/planeconstraintdialog.cpp.o:planeconstraintdialog.cpp:(.text+0x90):
first defined here
collect2: ld returned 1 exit status
make[2]: ** [lib/forcefieldextension.so] Erro 1
make[1]: **
[libavogadro/src/extensions/CMakeFiles/forcefieldextension.dir/all] Erro 2
make: ** [all] Erro 2
Fernando Nakagawa
+55 43 99521697
On Fri, Aug 21, 2009 at 2:08 PM, Tim Vandermeersch <
tim.vandermeersch@gmail.com> wrote:
On Fri, Aug 21, 2009 at 5:33 PM, Fernando Nakagawanaka86@gmail.com
wrote:Ahh the error that was thrown is:
make[2]: *** Sem regra para processar o alvo
../libavogadro/src/extensions/ planeconstraintdialog.ui', necessário porlibavogadro/src/extensions/ui_
planeconstraintdialog.h’. Pare.
make[1]: **
[libavogadro/src/extensions/CMakeFiles/forcefieldextension.dir/all] Erro
2
make: ** [all] Erro 2*** Sem regra para processar o alvo = no rule to make target
Fernando Nakagawa
It seems like the white space is causing the problems:
`…/libavogadro/src/extensions/ planeconstraintdialog.ui’
In the CMakeLists.txt file, make sure to remove all (there is only
one) spaces in
“forcefielddialog.ui;constraintsdialog.ui;conformersearchdialog.ui;
planeconstraintdialog.ui”CMakeLists.txt are part of the cmake build system. There is
documentation available on www.cmake.org or just google cmake.Tim
On Fri, Aug 21, 2009 at 11:32 AM, Fernando Nakagawa naka86@gmail.com
wrote:Hey there!
Well, actually I’m trying to add an extension to avogadro, so maybe
that’s
the reason it threw those problems. But I’m still having some trouble.
At
first I added planeconstraintdialog.cpp, planeconstraintdialog.h and
planeconstraintdialog.ui in the same extensions directory. I made some
modifications to forcefielextension.cpp and forcefieldextension.h (as
far as
I know the plane constraint dialog that Leandro created belongs to force
field extension) and to CMakeLists.txt.
I guess it’s the CMakeLists.txt, because when I change it, different
errors occur. I also dont know how to use the CMakeLists correctly, is there something I can read to know more about it? In annex are the files I have added and modified. In CMakeLists the trouble is on "Molecular Mechanics force fields". I hope its a silly
problem.Thanks for helping!
Fernando Nakagawa
On Tue, Aug 18, 2009 at 8:46 PM, Marcus D. Hanwell marcus@cryos.org
wrote:On Tuesday 18 August 2009 17:36:17 Fernando Nakagawa wrote:
Hello,
My name is Fernando Nakagawa and I’m continuing the work that Leandro
Boscariol made last year as a part of my master graduation. Well, I
saw
that avogadro has modified a lot since then, so I’m working on
porting
his
code to make avogadro runs, but I’m having some problems here. It
seems
that it compiles, but when linking it give me some errors. Somebody
have
any idea what it could be?Nice to meet you all!
Fernando Nakagawa
It looks like you are using an old version of Avogadro, or have stale
plugins
around. The plugins no longer use the lib prefix - so it would be
forcefieldextension.so. Did you checkout the latest sources using git?
See the
instructions below,http://avogadro.openmolecules.net/wiki/Compiling_on_Linux_and_Mac_OS_X
http://avogadro.openmolecules.net/wiki/Working_With_GitIf you have trouble then please let me know.
Thanks,
Marcus
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day
trial. Simplify your report design, integration and deployment - and
focus
on
what you do best, core application coding. Discover what’s new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
avogadro-devel List Signup and Options
Hey guys!
I just resolved the problem… thanks… it was a “hidden” include in the last
line of that class
Fernando Nakagawa
On Fri, Aug 21, 2009 at 5:32 PM, Fernando Nakagawa naka86@gmail.com wrote:
Hi guys!
After that silly problem, I`m still having trouble. I hope to be useful
after knowing how to get rid of these problems, and not to be disturbing
right now.
Well… somebody have a clue for this?Linking CXX shared module …/…/…/lib/forcefieldextension.so
CMakeFiles/forcefieldextension.dir/moc_planeconstraintdialog.cxx.o: In
functionAvogadro::PlaneConstraintDialog::metaObject() const': moc_planeconstraintdialog.cxx:(.text+0x0): multiple definition ofAvogadro::PlaneConstraintDialog::metaObject() const’
CMakeFiles/forcefieldextension.dir/planeconstraintdialog.cpp.o:planeconstraintdialog.cpp:(.text+0x10):
first defined here
CMakeFiles/forcefieldextension.dir/moc_planeconstraintdialog.cxx.o:(.
data.rel.ro+0x0): multiple definition of
Avogadro::PlaneConstraintDialog::staticMetaObject' CMakeFiles/forcefieldextension.dir/planeconstraintdialog.cpp.o:(. data.rel.ro+0x0): first defined here CMakeFiles/forcefieldextension.dir/moc_planeconstraintdialog.cxx.o: In functionAvogadro::PlaneConstraintDialog::qt_metacall(QMetaObject::Call,
int, void**)‘:
moc_planeconstraintdialog.cxx:(.text+0x70): multiple definition of
Avogadro::PlaneConstraintDialog::qt_metacall(QMetaObject::Call, int, void**)' CMakeFiles/forcefieldextension.dir/planeconstraintdialog.cpp.o:planeconstraintdialog.cpp:(.text+0x8b0): first defined here CMakeFiles/forcefieldextension.dir/moc_planeconstraintdialog.cxx.o: In functionAvogadro::PlaneConstraintDialog::qt_metacast(char const*)’:
moc_planeconstraintdialog.cxx:(.text+0xe0): multiple definition of
`Avogadro::PlaneConstraintDialog::qt_metacast(char const*)’
CMakeFiles/forcefieldextension.dir/planeconstraintdialog.cpp.o:planeconstraintdialog.cpp:(.text+0x90):
first defined here
collect2: ld returned 1 exit status
make[2]: ** [lib/forcefieldextension.so] Erro 1
make[1]: **
[libavogadro/src/extensions/CMakeFiles/forcefieldextension.dir/all] Erro 2
make: ** [all] Erro 2Fernando Nakagawa
+55 43 99521697On Fri, Aug 21, 2009 at 2:08 PM, Tim Vandermeersch <
tim.vandermeersch@gmail.com> wrote:On Fri, Aug 21, 2009 at 5:33 PM, Fernando Nakagawanaka86@gmail.com
wrote:Ahh the error that was thrown is:
make[2]: *** Sem regra para processar o alvo
../libavogadro/src/extensions/ planeconstraintdialog.ui', necessário porlibavogadro/src/extensions/ui_
planeconstraintdialog.h’. Pare.
make[1]: **
[libavogadro/src/extensions/CMakeFiles/forcefieldextension.dir/all] Erro
2
make: ** [all] Erro 2*** Sem regra para processar o alvo = no rule to make target
Fernando Nakagawa
It seems like the white space is causing the problems:
`…/libavogadro/src/extensions/ planeconstraintdialog.ui’
In the CMakeLists.txt file, make sure to remove all (there is only
one) spaces in
“forcefielddialog.ui;constraintsdialog.ui;conformersearchdialog.ui;
planeconstraintdialog.ui”CMakeLists.txt are part of the cmake build system. There is
documentation available on www.cmake.org or just google cmake.Tim
On Fri, Aug 21, 2009 at 11:32 AM, Fernando Nakagawa naka86@gmail.com
wrote:Hey there!
Well, actually I’m trying to add an extension to avogadro, so maybe
that’s
the reason it threw those problems. But I’m still having some trouble.
At
first I added planeconstraintdialog.cpp, planeconstraintdialog.h and
planeconstraintdialog.ui in the same extensions directory. I made some
modifications to forcefielextension.cpp and forcefieldextension.h (as
far as
I know the plane constraint dialog that Leandro created belongs to
force
field extension) and to CMakeLists.txt.
I guess it’s the CMakeLists.txt, because when I change it, different
errors occur. I also dont know how to use the CMakeLists correctly, is there something I can read to know more about it? In annex are the files I have added and modified. In CMakeLists the trouble is on "Molecular Mechanics force fields". I hope its a silly
problem.Thanks for helping!
Fernando Nakagawa
On Tue, Aug 18, 2009 at 8:46 PM, Marcus D. Hanwell marcus@cryos.org
wrote:On Tuesday 18 August 2009 17:36:17 Fernando Nakagawa wrote:
Hello,
My name is Fernando Nakagawa and I’m continuing the work that
Leandro
Boscariol made last year as a part of my master graduation. Well, I
saw
that avogadro has modified a lot since then, so I’m working on
porting
his
code to make avogadro runs, but I’m having some problems here. It
seems
that it compiles, but when linking it give me some errors. Somebody
have
any idea what it could be?Nice to meet you all!
Fernando Nakagawa
It looks like you are using an old version of Avogadro, or have stale
plugins
around. The plugins no longer use the lib prefix - so it would be
forcefieldextension.so. Did you checkout the latest sources using git?
See the
instructions below,http://avogadro.openmolecules.net/wiki/Compiling_on_Linux_and_Mac_OS_X
http://avogadro.openmolecules.net/wiki/Working_With_Git
If you have trouble then please let me know.
Thanks,
Marcus
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day
trial. Simplify your report design, integration and deployment - and
focus
on
what you do best, core application coding. Discover what’s new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
avogadro-devel List Signup and Options