Hello Bruno,

Thank you for the information, I will apply these to my project.

I ran a test where I copied the the source code for step-1 into another 
project in my IDE. I have everything setup the same way as my own 
application. 

I as able to compile step-1 and run it within the IDE without any issues. 
Maybe I am referencing something in my own code that is not being reference 
in the step-1

On Friday, May 4, 2018 at 8:33:27 AM UTC-4, Bruno Turcksin wrote:
>
> Philip,
>
> You can do what you are doing but this is really error prone. Two things 
> that can help you:
> 1) don't move libdeal_II.so but add the path to your LD_LIBRARY_PATH: 
> export LD_LIBRARY_PATH=/path/to/lib:$LD_LIBRARY_PATH
> 2) you want to use the flags in lib/cmake/deal.II/deal.IIConfig.cmake In 
> this file you will find all the flags and include path that are used by 
> cmake to compile an application. You need to use the same.
>
> Best
>
> Bruno
>
> On Thursday, May 3, 2018 at 10:20:12 PM UTC-4, phillip mobley wrote:
>>
>>
>> Hello all,
>>
>> I am getting an odd error where the program is not able to find a 
>> particular reference to one of the packages. 
>>
>> The error is listed below:
>>
>> ./Debug/main.cpp.o:(.rodata._ZTVN6dealii7DataOutILi2ENS_10DoFHandlerILi2ELi2EEEEE[_ZTVN6dealii7DataOutILi2ENS_10DoFHandlerILi2ELi2EEEEE]+0x28):
>>  
>> undefined reference to `dealii::DataOut_DoFData<dealii::DoFHandler<2, 2>, 
>> 2, 2>::get_dataset_names[abi:cxx11]() const'
>>
>> ./Debug/main.cpp.o:(.rodata._ZTVN6dealii7DataOutILi2ENS_10DoFHandlerILi2ELi2EEEEE[_ZTVN6dealii7DataOutILi2ENS_10DoFHandlerILi2ELi2EEEEE]+0x30):
>>  
>> undefined reference to `dealii::DataOut_DoFData<dealii::DoFHandler<2, 2>, 
>> 2, 2>::get_vector_data_ranges[abi:cxx11]() const'
>>
>> ./Debug/main.cpp.o:(.rodata._ZTVN6dealii4FE_QILi2ELi2EEE[_ZTVN6dealii4FE_QILi2ELi2EEE]+0x28):
>>  
>> undefined reference to `dealii::FE_Q<2, 2>::get_name[abi:cxx11]() const'
>>
>> I installed dealii according to the directions outlined here:
>>
>> http://dealii.org/8.5.0/readme.html
>>
>> Now, I do understand that it is recommended to use the cmake files 
>> however, I am linking directly to the library that was generated. I am 
>> following my own directions located here:
>>
>>
>>    1. 
>>    
>>    In the compiler settings, you need to make sure that the include 
>>    paths are to your installation for dealII.Both for the sources and what 
>> is 
>>    bundled. Ex. /home/phillip/dealii851/include and 
>>    /home/phillip/dealii851/include/deal.II/bundled
>>    2. 
>>    
>>    In the linker settings, have the linker library search path point to 
>>    the dealii installation director with the lib folder. And, place in the 
>>    library name in the Libraries option Ex Path -> 
>> /home/phillip/dealii851/lib 
>>    Library -> libdeal_II
>>    3. 
>>    
>>    In order to actually run a program (steps 1 and 2 will allow you to 
>>    compile the application), you need to copy the library 
>> libdeal_II.so.8.5.1 
>>    from the lib folder in the installation directory of DealII to the 
>> /usr/lib 
>>    folder
>>    
>>
>> Long story short, my application requires me to do this. (Maybe I just 
>> don't know how to use CMAKE too well). Basically, my application, I ma 
>> developing a GUI that will use dealii as the solver. So I am not sure how 
>> cmake will interact with the GUI library files that do not use cmake?
>>
>>
>> Anyways, I found that this is an easier procedure. 
>>
>>
>> What is odd is that this code that I am compiling works fine on another 
>> machine and I generated my procedure from the working machine. Has anyone 
>> received a set of errors similar to this?
>>
>>
>>

-- 
The deal.II project is located at http://www.dealii.org/
For mailing list/forum options, see 
https://groups.google.com/d/forum/dealii?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to