No, adding this header into all the AllJoyn/qcc header files is definitely 
cumbersome, and not normal. That’s not what I’m suggesting. But you might be 
able to unblock yourself quickly by #include’ing the standard header file in 
your app code before your app code #include’s AllJoyn’s header files, as a 
temporary solution.

As you get a better idea of what the problem is, please do open a JIRA ticket 
(linked from the contributing page I provided below) with as much information 
as you have, particularly with detail about your build environment and 
toolchain, so we’re tracking this issue and can reproduce it if need be. And if 
you have the time and inclination to contribute a fix, even better!

From: Brad Kemp [mailto:b...@beechwoods.com]
Sent: Wednesday, October 12, 2016 6:20 AM
To: Smooth Operator <osmoot...@gmail.com>
Cc: Kevin Kane <kk...@microsoft.com>; Mathew Martineau 
<allseen-core@lists.allseenalliance.org>
Subject: Re: [Allseen-core] Ubuntu/Eclipse + Cross Compile + Basicclient & 
Service

I found that the cross compiler installed via the apt utilities caused all 
kinds of problems. I went and built the toolchain using cross-ng and it build 
fine.
This was two or so years ago so the apt cross compiler may have been upgraded 
since then.
Brad

On Oct 12, 2016, at 4:26 AM, Smooth Operator 
<osmoot...@gmail.com<mailto:osmoot...@gmail.com>> wrote:

Hi Kevin, Thanks for your response. I have warnings with many header files, 
sorry if I was a bit unclear. I wanted to check if I was missing something 
important on eclipse (linux) while buildling, adding this header into all other 
Alljoyn/qcc header files I feel that's a bit cumbersome? is that normal?

I most certainly will contribute, but I need to first sort out a proper 
development environment where I can cross-compile regularly to ARM architecture 
based devices, can't use command line all the time, I'm sorry.

On Tue, Oct 11, 2016 at 9:41 PM, Kevin Kane 
<kk...@microsoft.com<mailto:kk...@microsoft.com>> wrote:
Hi Kiran,

I don’t have any knowledge of building for Raspberry Pi, but I’ll try to help 
you. uint32_t is a standard C99 type that should be defined by the standard 
headers AllJoyn relies on, but if not, try to #include <stdint.h> or 
<inttypes.h> before you #include any AllJoyn headers in your code.

If you spot places in our code that could benefit from fixes to support 
building on Raspberry Pi, please consider contributing them!

https://allseenalliance.org/framework/contribute

From: 
allseen-core-boun...@lists.allseenalliance.org<mailto:allseen-core-boun...@lists.allseenalliance.org>
 
[mailto:allseen-core-boun...@lists.allseenalliance.org<mailto:allseen-core-boun...@lists.allseenalliance.org>]
 On Behalf Of Smooth Operator
Sent: Tuesday, October 11, 2016 4:30 AM
To: 
allseen-core@lists.allseenalliance.org<mailto:allseen-core@lists.allseenalliance.org>
Subject: [Allseen-core] Ubuntu/Eclipse + Cross Compile + Basicclient & Service

Hello all

I'm very new to Alljoyn and rusty with c++ coding, I envisage to use alljoyn to 
program a raspberry pi running a DHT22 sensor. But I'm stuck in the first step 
itself I feel there are no clear instructions for a beginner to pick-up alljoyn 
and start their developing skills. Anyways I hope someone can help me, the 
first step I'm trying to build is a sample program client and service compiled 
on eclipse on Ubuntu/Eclipse, I've included the folders alljoyn and gcc in the 
includes settings on ecplise and trying to compile, I'm receiving the following 
error

     const uint16_t GetSpecificationVersion() const
           ^
/home/kiran/project/alljoyn/build/linux/x86_64/debug/dist/cpp/inc/alljoyn/PermissionPolicy.h:672:21:
 error: ‘uint32_t’ has not been declared
     void SetVersion(uint32_t version)
                     ^
/home/kiran/project/alljoyn/build/linux/x86_64/debug/dist/cpp/inc/alljoyn/PermissionPolicy.h:676:11:
 error: ‘uint32_t’ does not name a type
     const uint32_t GetVersion() const

Please can you help me?

Thanks
Kiran



_______________________________________________
Allseen-core mailing list
Allseen-core@lists.allseenalliance.org<mailto:Allseen-core@lists.allseenalliance.org>
https://lists.allseenalliance.org/mailman/listinfo/allseen-core

_______________________________________________
Allseen-core mailing list
Allseen-core@lists.allseenalliance.org
https://lists.allseenalliance.org/mailman/listinfo/allseen-core

Reply via email to