@Mayank Goyal Thank you for reaching out! As a community practice, we try to stay away from personal messages. So let's have a conversation here instead. :)
Regarding your question - our docs are at http://brlcad.org/wiki/Main_page
Himanshu Sekhar Nayak I recommend a side-by-side checkout of brlcad/trunk (the usual) and rt^3/trunk.
just done and still there is no
doc
directory
There shouldn't be a doc directory, but in your build log there were lines like /home/himanshu/brlcad-code/rt%5E3/doc/docbook/system/../resources/brlcad/brlcad-man-xhtml-stylesheet.xsl
, which look wrong.
@Himanshu Sekhar Nayak switching to a better stream.
nice
@Daniel Rossberg btw I had given paths
export PATH="/usr/brlcad/bin:$PATH"
export MANPATH="/usr/brlcad/man:$MANPATH"
while making cmake ..
for rt^3
I don't think that setting MANPATH is necessary, but it shouldn't hurt.
it first throws error pointing to <brlcad/cicommon.h> where it shows no such file or dir found
then I change it to <cicommon.h>
and compiling process started but struck in 86 where build log shows towards doc
directory
But, there is no doc in rt^3! Where does it come from?
:\
hmm when the compilation terminated now I see there is doc
dir
@Daniel Rossberg now I see while using cmake ..
under rt^3, it is automatically creating a doc
dir
so after using make
it throws error
Daniel Rossberg now I see while using
cmake ..
under rt^3, it is automatically creating adoc
dir
I've never hear of this before.
:/
while svn checkout
there is no doc
dir at all
but after cmake ..
, now it have a doc
dir
and onwards make
, it throws error
CMake shouldn't change anything in the source code checkout directory but in the build directory only. And even there I don't have a doc directory.
You have to check-out brlcad/trunk and *rt^3/trunk* into separate directories (I hope you did).
Build and install the brlcad check-out. Then generate the rt^3 make files (again in a separate build directory).
okay let me again get start over
You have to check-out brlcad/trunk and *rt^3/trunk* into separate directories (I hope you did).
I kept rt^3 under brlcad dir
You have to check-out brlcad/trunk and *rt^3/trunk* into separate directories (I hope you did).
I kept rt^3 under brlcad dir
This could be the cause. In this case, the doc directory was the one from brlcad.
https://paste.ofcode.org/eBKxX2UVHZkPnJ3wjkPbqp @Daniel Rossberg
should I compile again brlcad and then go to compile rt^3 dir ?
even giving the path, it doesn't resolve it
should I compile again brlcad and then go to compile rt^3 dir ?
I would say yes. I would even recommend to clean up the brlcad source code directory to remove all rt^3 stuff there and restore the original brlcad files there.
okay
I'm afraid, you have a mess there now :scream:
deleted brlcad dir and rt^3 now, doing a fresh start :)
I didn't dare to require this.
make clean
?
that one ?
no: rm -R brlcad
i did rm -rf brlcad
:\
or, in your case rm -R brl-code
:)
can i check size of a dir through ls
?
I know it's shows inside file and dirs
but still is there any way ?
can i check size of a dir through
ls
?
du
du -sh
is probable the command you are looking for.
You should have two directories:
Check out https://svn.code.sourceforge.net/p/brlcad/code/brlcad/trunk into the first one and https://svn.code.sourceforge.net/p/brlcad/code/rt^3/trunk into the second one.
Then, you could create directories for the build:
himanshu@asus:~
$ du -sh brlcad-code/
823M brlcad-code/
thanks @Daniel Rossberg
:)
himanshu@asus:~ $ du -sh brlcad-code/ 823M brlcad-code/
My source code check-out has 1003M.
As install directory for brlcad I recommend something in your home directory. This way, you don't need root privileges. E.g. /home/himanshu/bin/brlcad
that's why I used sudo make install
during compilation of brlcad
bye @Daniel Rossberg see you later. 1:18 AM here
Good night ...
@Daniel Rossberg when using export I saw one release
dir and development
dir for including bin
directory:$PATH . But I chosen release/bin
. Is it release or development that should I choose for may task ?
https://paste.ofcode.org/9JqYGaQPgJaysyQKEViRnh
@Himanshu Sekhar Nayak Development. Release should only be used for performance comparisons.
okay
all ya'll, do not use release unless you know why you need to use release. If you don't know, use debug.
okay got it
thanks @Erik got compiled successfully
okay I got the rt^3 source compilation done
but I didn't understand this
Build the coreinterface, printTitle, embeddedlua, and hellobrlcad targets
I headed towards rt^3/build/src
dir and found only coreinterface
and embeddedlua
but printTitle
and hellobrlcad
are in rt^3/build/tests-bin
Hi @Daniel Rossberg How I can produce Dynamic exception specifications are deprecated in C++11
warnings as *.h files mentioned in my task are not present in coreinterface rather present in rt^3/include/brlcad
himanshu@asus:~/brl-code/rt^3/include/brlcad
$ ls
Arb8.h Cone.h globals.h Object.h Sketch.h
Arb8.h.gch ConstDatabase.h Halfspace.h ParabolicCylinder.h Sphere.h
BagOfTriangles.h Database.h HyperbolicCylinder.h Paraboloid.h Torus.h
brlcadversion.h Ellipsoid.h Hyperboloid.h Particle.h Unknown.h
cicommon.h EllipticalTorus.h MemoryDatabase.h Pipe.h
Combination.h FileDatabase.h NonManifoldGeometry.h readme.txt
btw I created build
dir and done cmake ..
and make
but it doesn't even show warnings
may be I am in wrong path :\
any way I can produce those warnings ?
The header files are in include/brlcad and the corresponding source files in src/coreInterface.
any way I can produce those warnings ?
The warnings come with a recent compiler, e.g. gcc 8.3.0, if you haven't switched them of in CMake.
~/Devel/BRL-CAD/rt^3/include/brlcad/Sphere.h:40:30: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated] double radius)throw(bad_alloc); ^~~~~
looks like I am running 6.3 version of gcc
gcc 6.3.0 may be to old for the warnings. But, you can do the throw statement removement nevertheless.
(I'm running Debian buster, the current stable release.)
Just remove all the throws.
himanshu@asus:~
$ uname -a
Linux asus 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+mx17+1 (2019-11-17) x86_64 GNU/Linux
can I update gcc or something to check those warnings ?
@Daniel Rossberg is debian buster version is 10 ?
himanshu@asus:~
$ cat /etc/debian_version
9.11
oops I am in stretch version
I've 10.2. There's only gcc 7 and 8 here, with 8 being the default.
However, you can upgrade if you want, but you do not have to upgrade to do the task.
MX linux 18.3 cannot be upgraded to debian buster sadly
I have to download MX 19 and do a clean install
btw any other way I can produce the warnings ?
btw any other way I can produce the warnings ?
I don't know. Maybe, there is a flag for gcc 6 I don't know about. But, they are rather ugly and many. I don't like to see them :wink:
@Daniel Rossberg what if I use clang ?
or what if I svn gcc and make install in my distro ?
Try it. There is an own task for compiling BRL-CAD with clang, if I remember correctly.
yeah correct
then I have to migrate from gcc tp clang
*to
I have submitted my task at 11:30 am for review (https://codein.withgoogle.com/dashboard/task-instances/4605933116719104/)
It is a humble request if any one could review it, plz
:\
:\
I have to migrate
I have to migrate
Why do you "have to"?
If MX Linux is based on Debian, you could eventually upgrade to a stock Debian.
Sadly mx Linux is not a rolling release
Have to migrate
I have converted a .obj file to .g file
Now when i open it , how can I view it?
What tasks should i work on next, daniel?
i can program but still a newbie
First, I recommend to do the tutorials. This way, you learn more about BRL-CAD and its features.
Then, because you know already rt^3, you could work with the Lua binding. There are currently two tasks open (will be more): Object and Halfspace. Object is the base class of every database object and Halfspace is a very simple primitive, where already a stub exists. The bindings for Object can be separated in Lua as well, see objectbase.h.
I saw thos Lua tasks but i don't know that much either about Lua or C++
I was thinking about doing Appleseed series of tasks
Appleseed is worth a view for sure. You can start with the first one and see how far you get.
ok
i will try doing them
i am learning more in this competition(or whatever it is), more than the c++ books (they teach me theory ) lying around in my home
Keep asking here. But, keep in mind that because we don't see what you are actually doing, we may have some questions to you :wink:
ok
@Sumagna Das remember that we mentors are here to help you to some extent too, so I would suggest trying some coding tasks and just see how it goes, even if it's a language or technology you don't (yet) know. You just might learn something ;)
for what it's worth, the appleseed task set is not easier than the lua/c++ tasks. the first three are intentionally easy, but the rest require harder work. I would suggest trying one of the other coding tasks that are even simpler for starters (there are at least a half dozen
Hey @Daniel Rossberg If I have to bind function in lua so is it also compulsory to implement function of nested class too ?
(deleted)
The Appleseed series of tasks are pretty good anyways @Sean as you were telling
Last updated: Jan 10 2025 at 00:48 UTC